Gathering detailed insights and metrics for @cosmjs/launchpad
Gathering detailed insights and metrics for @cosmjs/launchpad
Gathering detailed insights and metrics for @cosmjs/launchpad
Gathering detailed insights and metrics for @cosmjs/launchpad
@cosmjs/cosmwasm-launchpad
CosmWasm SDK for Launchpad
@cosmjs/launchpad-ledger
A library for interacting with the Cosmos Launchpad Ledger Nano App
@cosmjs-rn/launchpad
A client library for the Cosmos SDK 0.37 (cosmoshub-3), 0.38 and 0.39 (Launchpad)
@cosmjs-rn/amino
Helpers for Amino based signing which are shared between @cosmjs-rn/launchpad and @cosmjs-rn/stargate.
The Swiss Army knife to power JavaScript based client solutions ranging from Web apps/explorers over browser extensions to server-side clients like faucets/scrapers.
npm install @cosmjs/launchpad
Typescript
Module System
TypeScript (94.02%)
JavaScript (3.43%)
Shell (2.21%)
Python (0.16%)
HTML (0.1%)
Dockerfile (0.07%)
CSS (0.01%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
Apache-2.0 License
688 Stars
4,535 Commits
382 Forks
13 Watchers
36 Branches
72 Contributors
Updated on Jul 11, 2025
Latest Version
0.27.1
Package Id
@cosmjs/launchpad@0.27.1
Unpacked Size
410.63 kB
Size
68.49 kB
File Count
117
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
7
36
CosmJS is the Swiss Army knife to power JavaScript based client solutions ranging from Web apps/explorers over browser extensions to server-side clients like faucets/scrapers in the Cosmos ecosystem.
"Cosm" is short for Cosmos and "JS" is short for runs everywhere – we actually develop in TypeScript.
Here is a list of examples using the Stargate package for use with Cosmos SDK 0.41 applications (like gaia 4). Take a look at the wiki page, "What can CosmJS do for me?" and various tests (ex) for more example usage of the packages.
The full API documentation is hosted at cosmos.github.io/cosmjs. This is a bit tricky to navigate and requires basic TypeScript understanding. It is helpful if you want to look up details for advanced use cases. This documentation is auto-generated based on the current main branch and can occasionally diverge from the latest release.
Documentation on how to use your own custom modules with CosmJS for Stargate chains (Cosmos SDK v0.41) can be found here.
CosmJS is a library that consists of many smaller npm packages within the @cosmjs namespace, a so-called monorepo. Here are some of them to get an idea:
Package | Description | Latest |
---|---|---|
@cosmjs/stargate | A client library for the Cosmos SDK 0.40+ (Stargate) | |
@cosmjs/faucet | A faucet application for node.js | |
@cosmjs/cosmwasm-stargate | Client for Stargate chains with the CosmWasm module enabled | |
@cosmjs/crypto | Cryptography for blockchain projects, e.g. hashing (SHA-2, Keccak256, Ripemd160), signing (secp256k1, ed25519), HD key derivation (BIP-39, SLIP-0010), KDFs and symmetric encryption for key storage (PBKDF2, Argon2, XChaCha20Poly1305) | |
@cosmjs/encoding | Encoding helpers for blockchain projects | |
@cosmjs/math | Safe integers; decimals for handling financial amounts |
We're pretty proud of the modularity and a clean dependency tree in this monorepo. This ensures software quality on our side and lets users pick exactly what they need. Here you see how everything fits together (every item is a npm package; right depends on left):
If this was not enough to scare you away, check out the version including app runtime dependencies: cosmjs-tree-full.png.
Currently the codebase supports the following runtime environments:
Our current JavaScript target standard is ES2020. We use WebAssembly to implement certain cryptographic functions.
We're happy to adjust this list according to users' needs as long as you don't ask for Internet Explorer support. If your environment does not support Wasm, we can work on a solution with swappable implementations.
With WebPack 5, you have to be explicit about the usage of Node.js types and modules that were simply replaced with re-implementations for browsers in Webpack 4.
Configs for 0.28 and later:
1module.exports = [ 2 { 3 // ... 4 plugins: [ 5 ..., 6 new webpack.ProvidePlugin({ 7 Buffer: ["buffer", "Buffer"], 8 }), 9 ], 10 // ... 11 resolve: { 12 fallback: { 13 buffer: false, 14 crypto: false, 15 events: false, 16 path: false, 17 stream: false, 18 string_decoder: false, 19 }, 20 }, 21 }, 22];
Configs for CosmJS < 0.28
1module.exports = [ 2 { 3 // ... 4 plugins: [ 5 ..., 6 new webpack.ProvidePlugin({ 7 Buffer: ["buffer", "Buffer"], 8 }), 9 ], 10 // ... 11 resolve: { 12 fallback: { 13 buffer: false, 14 crypto: false, 15 events: false, 16 path: false, 17 stream: require.resolve("stream-browserify"), 18 string_decoder: false, 19 }, 20 }, 21 }, 22];
There is no roadmap anymore. Just keeping things alive, nice and clean.
AuthExtension
and BankExtension
as well as
StargateClient.getAccountVerified
will fail because the storage keys are
not stable. Unverified queries can be used instead. Those queries are
deprecated now and will be removed in 0.27 (#910).AuthExtension
and all higher level Stargate clients only support
BaseAccount
s for all functionality, including getting account numbers and
sequences for transaction signing. This will be implemented for all common
Cosmos SDK account types in the 0.25 series.The CosmJS development team is happy to get in touch with you for all questions and suggestions.
#dev-chat
channel, or #dev-support-ai
on the
interchain Discord server for questions and
open discussionsSee HACKING.md.
No vulnerabilities found.
Reason
30 commit(s) and 11 issue activity found in the last 90 days -- score normalized to 10
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
packaging workflow detected
Details
Reason
SAST tool detected but not run on all commits
Details
Reason
Found 6/14 approved changesets -- score normalized to 4
Reason
dependency not pinned by hash detected -- score normalized to 2
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
project is not fuzzed
Details
Reason
security policy file not detected
Details
Reason
18 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More