@ledgerhq/coin-tester-solana
Ledger Solana Coin Tester
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 | encoded-string-file:lib/src/fixtures.js | AI (source-diff): Compiled output of fixtures.ts; same hex test data, not a payload. | ai | |
| source-diff | encoded-string-file:lib-es/src/fixtures.js | AI (source-diff): ESM compiled output of fixtures.ts; same hex test data, not a payload. | ai | |
| source-diff | encoded-string-file:src/fixtures.ts | AI (source-diff): Hex-encoded DER signatures and signed descriptors in MSW mock handlers; stable test fixture pattern for this package. | ai | |
| dependencies | unvetted-dep:@ledgerhq/live-signer-solana | AI (dependencies): First-party Ledger package from the same LedgerHQ/ledger-live monorepo; unvetted status reflects review queue lag, not a security concern. | ai | |
| provenance | no-provenance | AI (provenance): LedgerHQ publishes via CI without Sigstore provenance; consistent across their ecosystem and not a material risk signal. | ai | |
| dependencies | unvetted-dep:@ledgerhq/coin-framework | AI (dependencies): First-party LedgerHQ package from the same ledger-live monorepo; not a third-party risk. | ai | |
| dependencies | unvetted-dep:docker-compose | AI (dependencies): docker-compose is a standard dependency for integration test environments; appropriate for a coin-tester package in the LedgerHQ monorepo. | ai | |
| dependencies | unvetted-dep:ed25519-hd-key | AI (dependencies): ed25519-hd-key is a well-known HD key derivation library for Solana/ed25519; appropriate for a Solana coin tester. | ai | |
| dependencies | unvetted-dep:@ledgerhq/coin-tester | AI (dependencies): First-party LedgerHQ package from the same ledger-live monorepo; not a third-party risk. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): 127.0.0.1:8899 is the standard Solana test validator RPC endpoint; expected in a coin tester package that runs local integration tests. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding is used to deserialize Solana VersionedTransaction objects — standard Solana SDK usage, not obfuscation. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 1.20.0 | 16 / 10 | |
| 1.19.0 | 16 / 10 | |
| 1.18.0 | 16 / 10 | |
| 1.17.1 | 16 / 10 | |
| 1.17.0 | 16 / 10 | |
| 1.16.0 | 16 / 11 | |
| 1.15.0 | 15 / 9 | |
| 1.14.1 | 15 / 9 | |
| 1.14.0 | 15 / 9 | |
| 1.13.1 | 14 / 9 | |
| 1.13.0 | 14 / 9 | |
| 1.12.2 | 14 / 8 | |
| 1.12.1 | 14 / 8 | |
| 1.12.0 | 14 / 8 | |
| 1.11.1 | 14 / 8 | |
| 1.11.0 | 14 / 8 | |
| 1.10.1 | 14 / 8 | |
| 1.10.0 | 14 / 8 | |
| 1.9.0 | 14 / 7 | |
| 1.8.1 | 13 / 7 | |
| 1.8.0 | 13 / 7 | |
| 1.7.1 | 13 / 7 | |
| 1.6.2 | 13 / 7 | |
| 1.6.1 | 13 / 7 | |
| 1.1.0 | 13 / 7 |
v1.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.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.
v1.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
4 findingsModified file contains 6 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 6 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 6 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.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.