@dynamic-labs/solana-core
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from named npm account to GitHub Actions CI/CD is a standard automation migration for this org. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes Solana transaction buffers from base64 — standard blockchain SDK pattern, not obfuscation. | ai |
Versions (showing 9 of 210)
| Version | Deps | Published |
|---|---|---|
| 4.18.6 | 10 / 0 | |
| 4.18.5 | 10 / 0 | |
| 4.18.4 | 10 / 0 | |
| 4.18.3 | 10 / 0 | |
| 4.18.2 | 10 / 0 | |
| 4.18.1 | 10 / 0 | |
| 4.18.0 | 10 / 0 | |
| 4.17.0 | 10 / 0 | |
| 4.16.0 | 10 / 0 |
v4.18.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.