@ledgerhq/coin-framework
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 |
|---|---|---|---|---|
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decode usage is in a test file for BIP32 path comparison — standard test assertion pattern, not a malicious payload concern. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): uuid is a declared runtime dependency; phantom-dep heuristic fires because it's not directly imported in all source files but is legitimately used. | ai | |
| phantom-deps | phantom-dep:prando | AI (phantom-deps): prando is a declared runtime dependency used in bot/simulation contexts; phantom-dep heuristic is a stable false positive for this package. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 7.1.0 | 6 / 6 | |
| 7.0.0 | 6 / 6 | |
| 6.20.0 | 21 / 13 | |
| 6.19.0 | 21 / 13 | |
| 6.18.0 | 21 / 12 | |
| 6.17.0 | 21 / 12 | |
| 6.16.0 | 21 / 12 | |
| 6.15.0 | 21 / 12 | |
| 6.14.0 | 21 / 12 | |
| 6.13.1 | 20 / 12 | |
| 6.13.0 | 20 / 12 | |
| 6.12.0 | 20 / 11 | |
| 6.11.1 | 20 / 11 | |
| 6.11.0 | 20 / 11 | |
| 6.10.1 | 20 / 11 | |
| 6.10.0 | 20 / 11 | |
| 6.9.0 | 20 / 11 | |
| 6.8.0 | 19 / 10 |
v7.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.