@ledgerhq/zcash-shielded
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:tests/testAccounts.ts | AI (source-diff): Long lines are Zcash bech32 viewing keys and hex block/tx hashes in test fixtures — cryptographic test data, not obfuscation. Stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@ledgerhq/zcash-decrypt | AI (dependencies): @ledgerhq/zcash-decrypt is a first-party LedgerHQ package from the same monorepo/org; unvetted status reflects review lag, not a supply chain risk. | ai | |
| provenance | no-provenance | AI (provenance): LedgerHQ CI publishing pipeline does not currently attach Sigstore provenance; this is consistent across their monorepo releases and not a security concern. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.10.0 | 6 / 8 | |
| 0.9.1 | 5 / 8 | |
| 0.9.0 | 5 / 8 | |
| 0.8.0 | 5 / 8 | |
| 0.7.2 | 5 / 6 | |
| 0.7.1 | 5 / 6 | |
| 0.7.0 | 5 / 6 | |
| 0.6.0 | 5 / 6 | |
| 0.5.0 | 5 / 5 | |
| 0.4.0 | 2 / 4 | |
| 0.3.0 | 0 / 4 | |
| 0.2.0 | 0 / 4 |
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.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.7.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.
v0.7.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.