@cosmjs/tendermint-rpc
Tendermint RPC clients
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): willclarktech is listed as a named contributor in package.json and the package is part of the official cosmos/cosmjs monorepo; this is a legitimate team addition. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Version jump from 0.23.1 to 0.25.1 in an actively developed RPC client library; growth is consistent with legitimate feature additions in the cosmos/cosmjs project. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase reflects multi-version feature growth in an established CosmJS package; no obfuscation or suspicious payloads flagged. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped monorepo sub-package (@cosmjs); short README and no keywords are expected for sub-packages where docs live in the main repo. Not a spam/low-value package. | ai | |
| dependencies | unvetted-dep:readonly-date | AI (dependencies): readonly-date is a long-standing, well-known dependency of @cosmjs/tendermint-rpc used for immutable Date objects; stable across many versions. | ai | |
| dependencies | unvetted-dep:@cosmjs/json-rpc | AI (dependencies): First-party sibling package from the same cosmos/cosmjs monorepo; same publisher and version series. | ai | |
| dependencies | unvetted-dep:xstream | AI (dependencies): xstream is a well-established reactive streams library used throughout the CosmJS ecosystem; not a suspicious dependency. | ai | |
| dependencies | unvetted-dep:@cosmjs/utils | AI (dependencies): First-party sibling package from the same cosmos/cosmjs monorepo; same publisher and version series. | ai | |
| provenance | no-provenance | AI (provenance): CosmJS packages historically do not publish with Sigstore provenance; absence is consistent with prior versions and not a risk indicator for this publisher. | ai | |
| dependencies | unvetted-dep:readonly-date-esm | AI (dependencies): Small utility package for immutable Date objects; no known security concerns and appropriate for this use case. | ai | |
| dependencies | unvetted-dep:@cosmjs/crypto | AI (dependencies): First-party sibling package from the same cosmos/cosmjs monorepo; same publisher and version series. | ai | |
| dependencies | unvetted-dep:@cosmjs/socket | AI (dependencies): First-party sibling package from the same cosmos/cosmjs monorepo; same publisher and version series. | ai | |
| dependencies | unvetted-dep:@cosmjs/stream | AI (dependencies): First-party sibling package from the same cosmos/cosmjs monorepo; same publisher and version series. | ai | |
| dependencies | unvetted-dep:@cosmjs/encoding | AI (dependencies): First-party sibling package from the same cosmos/cosmjs monorepo; same publisher and version series. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.38.1 | 9 / 22 | |
| 0.38.0 | 9 / 22 | |
| 0.36.0 | 9 / 22 | |
| 0.25.1 | 9 / 1 | |
| 0.23.1 | 10 / 1 | |
| 0.38.0-rc.1 | 9 / 22 | |
| 0.36.2-0 | 9 / 22 |
v0.38.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0-rc.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.2-0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.