@cosmjs/proto-signing
Utilities for protobuf based signing (Cosmos SDK 0.40+)
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): CosmJS predates Sigstore provenance adoption; absence of attestation is expected for this package's publish workflow. | ai | |
| provenance | missing-githead | AI (provenance): webmaster128 has 485 approved releases; missing gitHead is a publish-environment change, not a security signal for this well-established CosmJS package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps (@cosmjs/crypto, @cosmjs/math, cosmjs-types) are all first-party CosmJS packages or the official cosmjs-types; consistent with the monorepo's own ecosystem. | ai | |
| source-diff | source-size-dropped | AI (source-diff): Size drop reflects migration of proto type generation to the cosmjs-types dependency; legitimate architectural refactoring, not code removal or stubbing. | ai | |
| provenance | publisher-changed | AI (provenance): willclarktech is a named contributor in package.json alongside webmaster128; the transition occurred in 2021 and is a documented team handoff within the cosmos/cosmjs project. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped monorepo package with established ecosystem presence; short README and no keywords are typical for this style of package, not spam indicators. | ai | |
| dependencies | unvetted-dep:@cosmjs/math | AI (dependencies): @cosmjs/math is a sibling package in the official CosmJS monorepo; expected dependency for this package across all versions. | ai | |
| dependencies | unvetted-dep:cosmjs-types | AI (dependencies): cosmjs-types is the standard protobuf type definitions package for CosmJS; expected and legitimate dependency. | ai | |
| dependencies | unvetted-dep:@cosmjs/crypto | AI (dependencies): @cosmjs/crypto is a sibling package in the official CosmJS monorepo; expected dependency for this package across all versions. | ai | |
| dependencies | unvetted-dep:@cosmjs/utils | AI (dependencies): @cosmjs/utils is a sibling package in the official CosmJS monorepo; expected dependency for this package across all versions. | ai | |
| dependencies | unvetted-dep:@cosmjs/amino | AI (dependencies): @cosmjs/amino is a sibling package in the official CosmJS monorepo; expected dependency for this package across all versions. | ai | |
| dependencies | unvetted-dep:@cosmjs/encoding | AI (dependencies): @cosmjs/encoding is a sibling package in the official CosmJS monorepo; expected dependency for this package across all versions. | ai |
Versions (showing 65 of 65)
| Version | Deps | Published |
|---|---|---|
| 0.39.0 | 6 / 24 | |
| 0.38.1 | 6 / 24 | |
| 0.38.0 | 6 / 24 | |
| 0.37.1 | 6 / 23 | |
| 0.37.0 | 6 / 23 | |
| 0.36.2 | 6 / 24 | |
| 0.36.1 | 6 / 24 | |
| 0.36.0 | 6 / 24 | |
| 0.35.2 | 6 / 24 | |
| 0.35.1 | 6 / 24 | |
| 0.35.0 | 6 / 24 | |
| 0.34.1 | 6 / 26 | |
| 0.34.0 | 6 / 26 | |
| 0.33.1 | 6 / 35 | |
| 0.33.0 | 6 / 35 | |
| 0.32.4 | 6 / 35 | |
| 0.32.3 | 6 / 35 | |
| 0.32.2 | 6 / 35 | |
| 0.32.1 | 6 / 35 | |
| 0.32.0 | 6 / 35 | |
| 0.31.3 | 7 / 35 | |
| 0.31.2 | 7 / 35 | |
| 0.31.1 | 7 / 35 | |
| 0.31.0 | 7 / 35 | |
| 0.30.1 | 7 / 35 | |
| 0.30.0 | 7 / 35 | |
| 0.29.5 | 7 / 35 | |
| 0.29.4 | 7 / 35 | |
| 0.29.3 | 7 / 35 | |
| 0.29.2 | 7 / 35 | |
| 0.29.1 | 7 / 35 | |
| 0.29.0 | 7 / 35 | |
| 0.28.13 | 7 / 35 | |
| 0.28.11 | 7 / 35 | |
| 0.28.10 | 7 / 35 | |
| 0.28.9 | 7 / 35 | |
| 0.28.7 | 7 / 35 | |
| 0.28.6 | 8 / 34 | |
| 0.28.4 | 8 / 34 | |
| 0.28.3 | 8 / 35 | |
| 0.28.2 | 8 / 35 | |
| 0.28.1 | 8 / 35 | |
| 0.28.0 | 6 / 37 | |
| 0.27.1 | 6 / 38 | |
| 0.27.0 | 6 / 38 | |
| 0.26.8 | 7 / 35 | |
| 0.26.6 | 6 / 38 | |
| 0.26.5 | 6 / 38 | |
| 0.26.4 | 6 / 38 | |
| 0.26.3 | 6 / 38 | |
| 0.26.2 | 6 / 38 | |
| 0.26.1 | 6 / 38 | |
| 0.26.0 | 6 / 38 | |
| 0.25.6 | 3 / 2 | |
| 0.25.5 | 3 / 2 | |
| 0.25.4 | 3 / 2 | |
| 0.25.3 | 3 / 2 | |
| 0.25.2 | 3 / 2 | |
| 0.25.1 | 3 / 2 | |
| 0.25.0 | 3 / 2 | |
| 0.24.1 | 3 / 2 | |
| 0.24.0 | 3 / 2 | |
| 0.38.0-rc.1 | 6 / 24 | |
| 0.37.0-rc.1 | 6 / 23 | |
| 0.36.2-0 | 6 / 23 |
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 findingPackage 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.8
1 findingPackage 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.
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.
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.
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.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.1
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.2
2 findingsThis version was published by a different npm account than previous versions on 2021-05-11. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.37.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.