@dynamic-labs-wallet/svm
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Consistent across Dynamic Labs scoped packages; not an indicator of malice for this publisher. | ai | |
| provenance | no-provenance | AI (provenance): Dynamic Labs packages consistently lack provenance attestation; not a risk signal for this org. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is used to parse raw Solana public keys for bs58 encoding — standard wallet SDK operation, not obfuscation. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped monorepo package published via CI; missing metadata is typical for internal SDK sub-packages. | ai |
Versions (showing 11 of 312)
| Version | Deps | Published |
|---|---|---|
| 0.0.37 | 4 / 0 | |
| 0.0.36 | 4 / 0 | |
| 0.0.35 | 4 / 0 | |
| 0.0.34 | 4 / 0 | |
| 0.0.33 | 4 / 0 | |
| 0.0.32 | 4 / 0 | |
| 0.0.31 | 4 / 0 | |
| 0.0.30 | 4 / 0 | |
| 0.0.29 | 4 / 0 | |
| 0.0.28 | 4 / 0 | |
| 0.0.1 | 4 / 0 |
v0.0.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.