@ledgerhq/coin-cardano
Ledger Cardano 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:@stricahq/typhonjs | AI (dependencies): @stricahq/typhonjs is the canonical Cardano JS library; expected dependency for a Cardano coin integration module. | ai | |
| dependencies | unvetted-dep:@stricahq/bip32ed25519 | AI (dependencies): @stricahq/bip32ed25519 is a standard Cardano cryptography library; expected for a Cardano coin integration. | ai | |
| dependencies | unvetted-dep:@ledgerhq/coin-framework | AI (dependencies): @ledgerhq/coin-framework is Ledger's own internal coin framework; expected dependency for all LedgerHQ coin modules. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding in this package is standard Cardano address handling (hex→bech32 conversion via typhonjs). This is core blockchain functionality, not a malicious payload pattern. | ai | |
| provenance | no-provenance | AI (provenance): Established Ledger HQ package published via CI account; lack of Sigstore provenance is common and not a risk signal for this package. | ai |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 0.25.5 | 18 / 10 | |
| 0.25.4 | 18 / 10 | |
| 0.25.3 | 18 / 10 | |
| 0.25.2 | 18 / 10 | |
| 0.25.1 | 18 / 10 | |
| 0.25.0 | 18 / 10 | |
| 0.24.0 | 18 / 10 | |
| 0.23.0 | 18 / 8 | |
| 0.22.0 | 18 / 8 | |
| 0.21.0 | 17 / 8 | |
| 0.20.0 | 17 / 8 | |
| 0.19.2 | 17 / 7 | |
| 0.19.1 | 17 / 7 | |
| 0.19.0 | 17 / 7 | |
| 0.18.2 | 17 / 7 | |
| 0.18.1 | 17 / 7 | |
| 0.18.0 | 17 / 7 | |
| 0.17.0 | 17 / 7 | |
| 0.16.2 | 17 / 6 | |
| 0.16.1 | 17 / 6 | |
| 0.16.0 | 17 / 6 | |
| 0.15.2 | 17 / 6 | |
| 0.15.1 | 17 / 6 | |
| 0.15.0 | 17 / 6 | |
| 0.14.0 | 17 / 6 | |
| 0.13.0 | 17 / 6 | |
| 0.12.3 | 17 / 6 | |
| 0.12.2 | 17 / 6 | |
| 0.12.1 | 17 / 6 | |
| 0.12.0 | 17 / 6 | |
| 0.11.2 | 17 / 6 | |
| 0.11.1 | 17 / 6 | |
| 0.11.0 | 17 / 6 | |
| 0.10.1 | 17 / 6 | |
| 0.10.0 | 17 / 6 | |
| 0.9.0 | 17 / 6 | |
| 0.8.12 | 17 / 6 | |
| 0.8.11 | 17 / 6 | |
| 0.8.10 | 17 / 6 | |
| 0.8.9 | 17 / 6 | |
| 0.8.8 | 17 / 7 | |
| 0.8.7 | 17 / 7 | |
| 0.8.6 | 17 / 7 | |
| 0.8.5 | 17 / 7 | |
| 0.8.4 | 17 / 6 | |
| 0.8.3 | 17 / 6 |
v0.25.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.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.22.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.15.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.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.