@dynamic-labs/solana
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 |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding is used to deserialize signed Solana transactions from WalletConnect — standard protocol usage, not obfuscation. | ai | |
| semgrep | semgrep:shady-links-tlds | AI (semgrep): Flags demo.dynamic.xyz — the package's own domain used as a localhost fallback in Phantom wallet redirect; not a suspicious TLD in context. | ai | |
| phantom-deps | phantom-dep:@wallet-standard/features | AI (phantom-deps): Type/config-only dependency in a monorepo; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@wallet-standard/experimental-features | AI (phantom-deps): Type/config-only dependency in a monorepo; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@dynamic-labs/sdk-api-core | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:@dynamic-labs/rpc-providers | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic is a stable false positive here. | ai |
Versions (showing 7 of 208)
| Version | Deps | Published |
|---|---|---|
| 4.18.4 | 17 / 0 | |
| 4.18.3 | 17 / 0 | |
| 4.18.2 | 17 / 0 | |
| 4.18.1 | 17 / 0 | |
| 4.18.0 | 17 / 0 | |
| 4.17.0 | 17 / 0 | |
| 4.16.0 | 17 / 0 |
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.