@cosmjs/json-rpc
Framework for implementing a JSON-RPC 2.0 API
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:xstream | AI (dependencies): xstream is a well-known reactive streams library that has been a stable dependency of @cosmjs/json-rpc across many versions; no security concerns associated with it. | ai | |
| provenance | missing-githead | AI (provenance): Trusted publisher (webmaster128) with 609 approved packages; missing gitHead reflects a publish environment change, not a security concern for this well-established CosmJS package. | ai | |
| provenance | publisher-changed | AI (provenance): willclarktech is a named contributor in package.json and a long-standing npm publisher (448 approved packages). The transition from webmaster128 is a documented CosmJS maintainer handoff, not a compromise. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped monorepo package from cosmos/cosmjs; short README and no keywords are expected for internal utility packages in this ecosystem. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): ethanfrey is a known CosmJS contributor; addition is consistent with legitimate project growth in the Cosmos ecosystem. | ai | |
| provenance | no-provenance | AI (provenance): CosmJS packages are published by a long-standing trusted publisher; lack of Sigstore provenance is common and not a risk signal for this package. | ai |
Versions (showing 51 of 72)
| Version | Deps | Published |
|---|---|---|
| 0.39.0 | 2 / 21 | |
| 0.38.1 | 2 / 21 | |
| 0.38.0 | 2 / 21 | |
| 0.37.1 | 2 / 21 | |
| 0.37.0 | 2 / 21 | |
| 0.36.2 | 2 / 21 | |
| 0.36.1 | 2 / 21 | |
| 0.36.0 | 2 / 21 | |
| 0.35.2 | 2 / 21 | |
| 0.35.1 | 2 / 21 | |
| 0.35.0 | 2 / 21 | |
| 0.34.1 | 2 / 23 | |
| 0.34.0 | 2 / 23 | |
| 0.33.1 | 2 / 32 | |
| 0.33.0 | 2 / 32 | |
| 0.32.4 | 2 / 32 | |
| 0.32.3 | 2 / 32 | |
| 0.32.2 | 2 / 32 | |
| 0.32.1 | 2 / 32 | |
| 0.32.0 | 2 / 32 | |
| 0.31.3 | 2 / 32 | |
| 0.31.2 | 2 / 32 | |
| 0.31.1 | 2 / 32 | |
| 0.31.0 | 2 / 32 | |
| 0.30.1 | 2 / 32 | |
| 0.30.0 | 2 / 32 | |
| 0.29.5 | 2 / 32 | |
| 0.29.4 | 2 / 32 | |
| 0.29.3 | 2 / 32 | |
| 0.29.2 | 2 / 32 | |
| 0.29.1 | 2 / 32 | |
| 0.29.0 | 2 / 32 | |
| 0.28.13 | 2 / 32 | |
| 0.28.11 | 2 / 32 | |
| 0.28.10 | 2 / 32 | |
| 0.28.9 | 2 / 32 | |
| 0.28.7 | 2 / 32 | |
| 0.28.6 | 2 / 32 | |
| 0.28.4 | 2 / 32 | |
| 0.28.3 | 2 / 33 | |
| 0.28.2 | 2 / 33 | |
| 0.28.1 | 2 / 33 | |
| 0.28.0 | 2 / 33 | |
| 0.27.1 | 2 / 33 | |
| 0.27.0 | 2 / 33 | |
| 0.26.8 | 2 / 32 | |
| 0.26.6 | 2 / 33 | |
| 0.26.5 | 2 / 33 | |
| 0.26.4 | 2 / 33 | |
| 0.26.3 | 2 / 33 | |
| 0.26.2 | 2 / 33 |
v0.39.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-05-04. This could indicate a legitimate maintainer transition or an account compromise.
v0.38.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.2
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.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.2
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.35.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.1
2 findingsThis version was published by a different npm account than previous versions on 2025-03-13. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.13
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.28.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: webmaster128.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: webmaster128.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: webmaster128.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: webmaster128.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: webmaster128.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.