@ledgerhq/coin-solana
Ledger Solana 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, 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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:lib-es/prepareTransaction.test.js | AI (source-diff): Base64 string is a Solana raw transaction fixture in a test file; not a malicious payload. | ai | |
| source-diff | encoded-string-file:lib/prepareTransaction.test.js | AI (source-diff): Same base64 Solana transaction fixture in CJS test file; benign test data. | ai | |
| source-diff | encoded-string-file:src/prepareTransaction.test.ts | AI (source-diff): Long encoded string is a base64 Solana transaction fixture in a test file — standard practice for blockchain SDK testing, not a malicious payload. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex-to-base64 conversion of Solana transaction signatures for RPC broadcast — standard blockchain SDK pattern, not payload obfuscation. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding of serialized Solana transactions before sendRawTransaction — canonical Solana RPC broadcast pattern, not malicious. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() used in a Proxy handler for API call logging/instrumentation — standard JavaScript pattern, not evasion. | ai |
Versions (showing 85 of 85)
| Version | Deps | Published |
|---|---|---|
| 0.58.0 | 20 / 15 | |
| 0.57.0 | 22 / 14 | |
| 0.56.0 | 22 / 14 | |
| 0.55.2 | 22 / 14 | |
| 0.55.1 | 22 / 14 | |
| 0.55.0 | 22 / 14 | |
| 0.54.0 | 22 / 14 | |
| 0.53.0 | 22 / 14 | |
| 0.52.0 | 22 / 15 | |
| 0.51.2 | 22 / 15 | |
| 0.51.1 | 22 / 15 | |
| 0.51.0 | 22 / 15 | |
| 0.50.0 | 22 / 15 | |
| 0.49.0 | 22 / 14 | |
| 0.48.0 | 22 / 14 | |
| 0.47.0 | 20 / 15 | |
| 0.46.0 | 20 / 15 | |
| 0.45.2 | 20 / 14 | |
| 0.45.1 | 20 / 14 | |
| 0.45.0 | 20 / 14 | |
| 0.44.0 | 20 / 14 | |
| 0.43.0 | 20 / 14 | |
| 0.42.0 | 20 / 14 | |
| 0.41.0 | 20 / 14 | |
| 0.40.0 | 20 / 15 | |
| 0.39.1 | 20 / 15 | |
| 0.39.0 | 20 / 15 | |
| 0.38.1 | 20 / 15 | |
| 0.38.0 | 20 / 15 | |
| 0.37.0 | 21 / 16 | |
| 0.36.0 | 21 / 16 | |
| 0.35.0 | 21 / 16 | |
| 0.34.1 | 21 / 16 | |
| 0.34.0 | 21 / 16 | |
| 0.33.0 | 21 / 16 | |
| 0.32.0 | 21 / 16 | |
| 0.31.1 | 21 / 16 | |
| 0.31.0 | 21 / 16 | |
| 0.30.0 | 21 / 16 | |
| 0.29.0 | 21 / 16 | |
| 0.28.0 | 21 / 16 | |
| 0.27.2 | 21 / 15 | |
| 0.27.1 | 21 / 15 | |
| 0.27.0 | 21 / 15 | |
| 0.26.0 | 21 / 15 | |
| 0.25.1 | 21 / 15 | |
| 0.25.0 | 21 / 16 | |
| 0.24.0 | 21 / 16 | |
| 0.23.0 | 21 / 16 | |
| 0.22.1 | 21 / 16 | |
| 0.22.0 | 21 / 16 | |
| 0.21.1 | 20 / 14 | |
| 0.21.0 | 20 / 14 | |
| 0.20.0 | 20 / 14 | |
| 0.19.0 | 20 / 14 | |
| 0.18.0 | 20 / 14 | |
| 0.17.0 | 20 / 13 | |
| 0.16.0 | 20 / 10 | |
| 0.15.1 | 19 / 8 | |
| 0.15.0 | 19 / 8 | |
| 0.14.0 | 19 / 8 | |
| 0.13.1 | 19 / 8 | |
| 0.13.0 | 19 / 8 | |
| 0.12.1 | 19 / 8 | |
| 0.12.0 | 19 / 8 | |
| 0.11.1 | 19 / 8 | |
| 0.11.0 | 19 / 8 | |
| 0.10.1 | 19 / 8 | |
| 0.10.0 | 19 / 8 | |
| 0.9.0 | 19 / 8 | |
| 0.8.6 | 19 / 8 | |
| 0.8.5 | 19 / 8 | |
| 0.8.4 | 19 / 8 | |
| 0.8.3 | 19 / 8 | |
| 0.8.2 | 19 / 8 | |
| 0.8.1 | 19 / 8 | |
| 0.8.0 | 19 / 8 | |
| 0.7.7 | 19 / 8 | |
| 0.7.6 | 19 / 8 | |
| 0.7.5 | 19 / 8 | |
| 0.7.4 | 19 / 8 | |
| 0.7.3 | 19 / 8 | |
| 0.7.2 | 19 / 8 | |
| 0.7.1 | 19 / 8 | |
| 0.7.0 | 19 / 8 |
v0.58.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.57.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.