@ledgerhq/coin-filecoin
Ledger Filecoin 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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Provenance attestation is not yet standard practice; absence is not a security concern for this established, ecosystem-trusted package. | ai | |
| dependencies | unvetted-dep:@zondax/cbor | AI (dependencies): Zondax is a known blockchain tooling company working with Ledger; @zondax/cbor is a domain-appropriate CBOR library for Filecoin integration. | ai | |
| dependencies | unvetted-dep:iso-filecoin | AI (dependencies): iso-filecoin is a standard Filecoin utility library; appropriate dependency for a Filecoin coin integration package. | ai | |
| phantom-deps | phantom-dep:@ledgerhq/devices | AI (phantom-deps): Same-org package declared as dependency in a large monorepo; phantom dep finding is a false positive for this package structure. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): hex-decode fires on a legitimate getBufferFromString utility in a blockchain library; decoding hex/base64 transaction data is expected behavior for a Filecoin coin integration. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): base64-decode fires on the same getBufferFromString utility; decoding base64 message data is standard for a blockchain/crypto library, not a malicious payload. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.24.3 | 17 / 12 | |
| 1.24.1 | 17 / 12 | |
| 1.24.0 | 17 / 12 | |
| 1.23.0 | 17 / 12 | |
| 1.22.1 | 17 / 10 | |
| 1.22.0 | 17 / 10 | |
| 1.18.1 | 16 / 9 | |
| 1.14.1 | 16 / 8 | |
| 1.9.4 | 16 / 8 |
v1.24.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.