@ledgerhq/coin-cosmos
Ledger Cosmos Coin integration
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@ledgerhq/coin-framework | AI (dependencies): @ledgerhq/coin-framework is a first-party Ledger package from the same LedgerHQ monorepo; unvetted status is a pipeline artifact, not a real risk for this package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding is used to encode public keys into protobuf structures for Cosmos transactions — standard cryptographic operation in a blockchain SDK, not a malicious payload. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding converts transaction signatures to bytes for broadcasting — standard blockchain SDK operation, not obfuscation or exfiltration. | ai | |
| provenance | no-provenance | AI (provenance): Established LedgerHQ package with clear GitHub repo linkage; lack of Sigstore provenance is common and not a meaningful risk signal here. | ai |
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 0.35.0 | 25 / 11 | |
| 0.34.1 | 25 / 11 | |
| 0.34.0 | 25 / 11 | |
| 0.33.1 | 25 / 11 | |
| 0.33.0 | 25 / 11 | |
| 0.32.1 | 25 / 11 | |
| 0.32.0 | 25 / 11 | |
| 0.31.0 | 25 / 11 | |
| 0.30.0 | 25 / 11 | |
| 0.29.1 | 25 / 9 | |
| 0.29.0 | 25 / 9 | |
| 0.28.0 | 24 / 9 | |
| 0.27.0 | 24 / 9 | |
| 0.26.0 | 24 / 8 | |
| 0.25.1 | 24 / 8 | |
| 0.25.0 | 24 / 8 | |
| 0.24.0 | 24 / 8 | |
| 0.23.2 | 24 / 8 | |
| 0.23.1 | 24 / 8 | |
| 0.23.0 | 24 / 8 | |
| 0.22.0 | 24 / 7 | |
| 0.21.1 | 25 / 7 | |
| 0.21.0 | 25 / 7 | |
| 0.20.2 | 25 / 7 | |
| 0.20.1 | 25 / 7 | |
| 0.20.0 | 25 / 7 | |
| 0.19.0 | 25 / 7 | |
| 0.18.0 | 25 / 7 | |
| 0.17.3 | 25 / 7 | |
| 0.17.2 | 25 / 7 | |
| 0.17.1 | 25 / 7 | |
| 0.17.0 | 25 / 7 | |
| 0.16.7 | 25 / 7 | |
| 0.16.6 | 25 / 7 | |
| 0.16.5 | 25 / 7 | |
| 0.16.4 | 25 / 7 | |
| 0.16.3 | 25 / 7 | |
| 0.16.2 | 25 / 7 | |
| 0.16.1 | 25 / 7 | |
| 0.16.0 | 25 / 7 | |
| 0.15.2 | 25 / 7 | |
| 0.15.1 | 25 / 7 | |
| 0.15.0 | 25 / 8 | |
| 0.14.3 | 25 / 8 | |
| 0.14.2 | 25 / 8 | |
| 0.14.1 | 25 / 8 | |
| 0.14.0 | 25 / 7 | |
| 0.13.2 | 25 / 7 |
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
1 finding[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.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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.30.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.29.1
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.29.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.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.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.13.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.