@ledgerhq/hw-ledger-key-ring-protocol
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
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 literals are hardcoded test vectors in unit tests, not runtime payload decoding. | ai | |
| phantom-deps | phantom-dep:@ledgerhq/logs | AI (phantom-deps): Same-org dependency; likely used transitively or via re-export pattern. | ai | |
| phantom-deps | phantom-dep:@ledgerhq/live-env | AI (phantom-deps): Same-org dependency; likely used transitively or via re-export pattern. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 0.10.7 | 6 / 9 | |
| 0.10.6 | 6 / 9 | |
| 0.10.5 | 6 / 9 | |
| 0.10.4 | 6 / 9 | |
| 0.10.3 | 6 / 9 | |
| 0.10.2 | 6 / 9 | |
| 0.10.1 | 6 / 9 | |
| 0.10.0 | 6 / 9 | |
| 0.9.2 | 6 / 7 | |
| 0.9.1 | 6 / 7 | |
| 0.9.0 | 6 / 7 | |
| 0.8.1 | 6 / 7 | |
| 0.8.0 | 6 / 7 | |
| 0.7.4 | 6 / 6 | |
| 0.7.3 | 6 / 6 | |
| 0.7.2 | 6 / 6 | |
| 0.7.1 | 6 / 6 | |
| 0.7.0 | 6 / 6 | |
| 0.6.1 | 6 / 5 | |
| 0.6.0 | 6 / 5 | |
| 0.5.6 | 6 / 5 | |
| 0.5.5 | 6 / 5 | |
| 0.5.4 | 6 / 5 | |
| 0.5.3 | 6 / 5 | |
| 0.5.2 | 6 / 5 | |
| 0.5.1 | 6 / 5 | |
| 0.5.0 | 6 / 5 | |
| 0.4.0 | 6 / 5 | |
| 0.3.13 | 7 / 5 | |
| 0.3.12 | 7 / 5 | |
| 0.3.11 | 7 / 5 | |
| 0.3.10 | 7 / 5 | |
| 0.3.9 | 7 / 5 | |
| 0.3.8 | 7 / 5 | |
| 0.3.7 | 7 / 5 | |
| 0.3.6 | 7 / 5 | |
| 0.3.5 | 7 / 5 | |
| 0.3.1 | 7 / 5 | |
| 0.3.0 | 7 / 5 | |
| 0.2.1 | 7 / 5 |
v0.10.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.