@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 — 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-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 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 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 |
v0.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.50.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.0
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.0
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.