@dynamic-labs-wallet/evm
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 internal scoped monorepo packages from this publisher. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Metadata gaps are consistent across the @dynamic-labs-wallet monorepo family; not indicative of spam or malice. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decode is used to convert viem-serialized EVM transaction bytes — standard blockchain SDK pattern, not obfuscation. | ai | |
| phantom-deps | phantom-dep:@faker-js/faker | AI (phantom-deps): @faker-js/faker appears in package.json deps but used only in test/config; stable false positive for this SDK package. | ai |
Versions (showing 22 of 223)
| Version | Deps | Published |
|---|---|---|
| 0.0.87 | 1 / 0 | |
| 0.0.86 | 1 / 0 | |
| 0.0.85 | 1 / 0 | |
| 0.0.84 | 1 / 0 | |
| 0.0.83 | 1 / 0 | |
| 0.0.82 | 1 / 0 | |
| 0.0.81 | 1 / 0 | |
| 0.0.80 | 1 / 0 | |
| 0.0.79 | 1 / 0 | |
| 0.0.78 | 1 / 0 | |
| 0.0.77 | 1 / 0 | |
| 0.0.76 | 1 / 0 | |
| 0.0.75 | 1 / 0 | |
| 0.0.74 | 1 / 0 | |
| 0.0.73 | 1 / 0 | |
| 0.0.72 | 1 / 0 | |
| 0.0.71 | 1 / 0 | |
| 0.0.70 | 1 / 0 | |
| 0.0.69 | 1 / 0 | |
| 0.0.68 | 1 / 0 | |
| 0.0.67 | 1 / 0 | |
| 0.0.66 | 1 / 0 |
v0.0.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.