@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, 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 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 86 of 288)
| Version | Deps | Published |
|---|---|---|
| 0.0.133 | 2 / 0 | |
| 0.0.132 | 2 / 0 | |
| 0.0.131 | 2 / 0 | |
| 0.0.130 | 2 / 0 | |
| 0.0.129 | 2 / 0 | |
| 0.0.128 | 2 / 0 | |
| 0.0.127 | 2 / 0 | |
| 0.0.126 | 2 / 0 | |
| 0.0.125 | 2 / 0 | |
| 0.0.124 | 2 / 0 | |
| 0.0.123 | 2 / 0 | |
| 0.0.122 | 2 / 0 | |
| 0.0.121 | 2 / 0 | |
| 0.0.120 | 2 / 0 | |
| 0.0.119 | 2 / 0 | |
| 0.0.118 | 2 / 0 | |
| 0.0.117 | 2 / 0 | |
| 0.0.116 | 2 / 0 | |
| 0.0.115 | 2 / 0 | |
| 0.0.114 | 2 / 0 | |
| 0.0.113 | 2 / 0 | |
| 0.0.112 | 2 / 0 | |
| 0.0.111 | 2 / 0 | |
| 0.0.110 | 2 / 0 | |
| 0.0.109 | 2 / 0 | |
| 0.0.108 | 2 / 0 | |
| 0.0.107 | 2 / 0 | |
| 0.0.106 | 2 / 0 | |
| 0.0.105 | 2 / 0 | |
| 0.0.104 | 2 / 0 | |
| 0.0.103 | 2 / 0 | |
| 0.0.102 | 2 / 0 | |
| 0.0.101 | 2 / 0 | |
| 0.0.100 | 2 / 0 | |
| 0.0.99 | 2 / 0 | |
| 0.0.98 | 2 / 0 | |
| 0.0.97 | 2 / 0 | |
| 0.0.95 | 2 / 0 | |
| 0.0.94 | 2 / 0 | |
| 0.0.93 | 2 / 0 | |
| 0.0.92 | 2 / 0 | |
| 0.0.91 | 2 / 0 | |
| 0.0.90 | 2 / 0 | |
| 0.0.89 | 2 / 0 | |
| 0.0.88 | 2 / 0 | |
| 0.0.87 | 2 / 0 | |
| 0.0.86 | 2 / 0 | |
| 0.0.85 | 2 / 0 | |
| 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.65 | 2 / 0 | |
| 0.0.64 | 2 / 0 | |
| 0.0.63 | 2 / 0 | |
| 0.0.62 | 2 / 0 | |
| 0.0.61 | 2 / 0 | |
| 0.0.60 | 2 / 0 | |
| 0.0.59 | 2 / 0 | |
| 0.0.58 | 2 / 0 | |
| 0.0.57 | 2 / 0 | |
| 0.0.56 | 2 / 0 | |
| 0.0.55 | 2 / 0 | |
| 0.0.54 | 2 / 0 | |
| 0.0.53 | 2 / 0 | |
| 0.0.52 | 2 / 0 | |
| 0.0.51 | 2 / 0 | |
| 0.0.50 | 2 / 0 | |
| 0.0.49 | 2 / 0 | |
| 0.0.48 | 2 / 0 | |
| 0.0.1 | 2 / 0 |
v0.0.65
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.64
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.63
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.62
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.61
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.60
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.59
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.58
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.57
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.56
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.55
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.54
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.53
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.52
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.51
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.50
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.49
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.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.