@dynamic-labs-wallet/node-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 — 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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Consistent with monorepo sub-package pattern for this publisher. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across all @dynamic-labs-wallet packages; consistent publisher pattern. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Decodes Solana public key bytes from hex strings — standard web3.js usage, not obfuscation. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes sponsored transaction bytes from base64 — standard Solana transaction handling. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal scoped SDK package; no repo/description is typical for monorepo-published sub-packages. | ai |
Versions (showing 20 of 221)
| Version | Deps | Published |
|---|---|---|
| 0.0.84 | 2 / 0 | |
| 0.0.83 | 2 / 0 | |
| 0.0.82 | 2 / 0 | |
| 0.0.81 | 2 / 0 | |
| 0.0.80 | 2 / 0 | |
| 0.0.79 | 2 / 0 | |
| 0.0.78 | 2 / 0 | |
| 0.0.77 | 2 / 0 | |
| 0.0.76 | 2 / 0 | |
| 0.0.75 | 2 / 0 | |
| 0.0.74 | 2 / 0 | |
| 0.0.73 | 2 / 0 | |
| 0.0.72 | 2 / 0 | |
| 0.0.71 | 2 / 0 | |
| 0.0.70 | 2 / 0 | |
| 0.0.69 | 2 / 0 | |
| 0.0.68 | 2 / 0 | |
| 0.0.67 | 2 / 0 | |
| 0.0.66 | 2 / 0 | |
| 0.0.1 | 2 / 0 |
v0.0.84
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.83
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.82
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.80
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.68
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.67
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.66
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.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.