@ledgerhq/device-trusted-app-kit-ledger-keyring-protocol
...
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:lib/cjs/internal/app-binder/task/SignChallengeWithKeypairTask.test.js | AI (source-diff): Long strings are hex-encoded cryptographic test vectors (ECDSA signatures, TLV challenge data, private keys) used as hardcoded fixtures in unit tests. Stable false positive for this crypto signing library. | ai | |
| source-diff | encoded-string-file:lib/esm/internal/app-binder/task/SignChallengeWithKeypairTask.test.js | AI (source-diff): Same as CJS counterpart — hex-encoded cryptographic test vectors in unit test fixtures. Stable false positive for this crypto signing library. | ai | |
| dependencies | unvetted-dep:purify-ts | AI (dependencies): purify-ts is a well-known functional programming library for TypeScript with no known advisories; its use here is legitimate and expected. | ai | |
| dependencies | unvetted-peer-dep:@ledgerhq/device-management-kit | AI (dependencies): First-party Ledger peer dependency; entirely expected within the LedgerHQ device SDK ecosystem. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.5.0 | 9 / 6 | |
| 0.4.1 | 9 / 6 | |
| 0.4.0 | 10 / 5 | |
| 0.3.1 | 10 / 5 | |
| 0.3.0 | 10 / 5 | |
| 0.2.0 | 10 / 5 |
v0.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.4.1
3 findingsModified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.