@solana/keychain-turnkey
Supply chain provenance
Status for the latest visible version.
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:dist/__tests__/turnkey-signer.test.js | AI (source-diff): Long string is a mock base64 Solana transaction in a test fixture, not a hidden payload. | ai | |
| source-diff | encoded-string-file:src/__tests__/turnkey-signer.test.ts | AI (source-diff): Same mock base64 transaction constant in test source; benign test data. | ai | |
| phantom-deps | phantom-dep:@solana/codecs-core | AI (phantom-deps): @solana/codecs-core is declared in dependencies; may be used transitively or indirectly. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Solana org uses 0.0.0 for namespace reservation stubs; not indicative of malicious intent. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Placeholder stub under official @solana scope; empty payload is intentional for namespace reservation. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Fires on a static test vector in a unit test file; no runtime payload risk. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.3.0 | 2 / 8 | |
| 1.2.0 | 2 / 8 | |
| 1.1.0 | 2 / 8 | |
| 1.0.1 | 2 / 8 | |
| 0.6.1 | 2 / 8 | |
| 0.6.0 | 8 / 2 | |
| 0.5.0 | 8 / 2 | |
| 0.4.0 | 8 / 2 | |
| 0.3.0 | 8 / 2 | |
| 0.2.1 | 8 / 2 | |
| 0.0.0 | 0 / 0 |
v1.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.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/v1). This is the strongest supply chain integrity signal.
v0.6.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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.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.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.