@dynamic-labs-wallet/node-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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from packaging-at-dynamic-labs to GitHub Actions CI is a standard automation migration for this org. | ai | |
| phantom-deps | phantom-dep:@dynamic-labs-wallet/core | AI (phantom-deps): Same-org dependency; re-exported transitively rather than directly imported in this wrapper. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decode is standard EVM tx serialization (strip 0x prefix); not obfuscation. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode is standard JWT payload parsing; not obfuscation. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo SDK package; missing metadata is expected for this namespace. | ai |
Versions (showing 51 of 239)
| Version | Deps | Published |
|---|---|---|
| 1.0.17 | 8 / 3 | |
| 1.0.16 | 8 / 3 | |
| 1.0.15 | 8 / 3 | |
| 1.0.14 | 8 / 3 | |
| 1.0.13 | 8 / 3 | |
| 1.0.12 | 8 / 3 | |
| 1.0.11 | 8 / 3 | |
| 1.0.10 | 8 / 3 | |
| 1.0.9 | 8 / 3 | |
| 1.0.8 | 8 / 3 | |
| 1.0.7 | 8 / 3 | |
| 1.0.6 | 8 / 3 | |
| 1.0.5 | 8 / 3 | |
| 1.0.4 | 8 / 3 | |
| 1.0.3 | 8 / 3 | |
| 1.0.2 | 8 / 3 | |
| 1.0.1 | 8 / 3 | |
| 1.0.0 | 8 / 3 | |
| 0.0.354 | 7 / 3 | |
| 0.0.353 | 7 / 3 | |
| 0.0.352 | 7 / 3 | |
| 0.0.351 | 7 / 3 | |
| 0.0.350 | 7 / 3 | |
| 0.0.349 | 7 / 3 | |
| 0.0.348 | 7 / 3 | |
| 0.0.346 | 7 / 3 | |
| 0.0.345 | 7 / 3 | |
| 0.0.344 | 7 / 3 | |
| 0.0.343 | 7 / 3 | |
| 0.0.342 | 7 / 3 | |
| 0.0.341 | 7 / 3 | |
| 0.0.340 | 7 / 3 | |
| 0.0.339 | 7 / 3 | |
| 0.0.338 | 7 / 3 | |
| 0.0.337 | 7 / 3 | |
| 0.0.336 | 7 / 3 | |
| 0.0.335 | 7 / 3 | |
| 0.0.334 | 7 / 3 | |
| 0.0.333 | 7 / 3 | |
| 0.0.332 | 7 / 3 | |
| 0.0.331 | 7 / 3 | |
| 0.0.330 | 7 / 3 | |
| 0.0.329 | 7 / 3 | |
| 0.0.328 | 7 / 3 | |
| 0.0.327 | 7 / 3 | |
| 0.0.326 | 7 / 3 | |
| 0.0.325 | 7 / 3 | |
| 0.0.324 | 7 / 3 | |
| 0.0.323 | 7 / 3 | |
| 0.0.322 | 7 / 3 | |
| 0.0.321 | 7 / 3 |
v1.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.354
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.353
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.352
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.351
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.350
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.349
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.348
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.346
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.345
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.344
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.343
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.342
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.341
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.340
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.339
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.338
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.337
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.336
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.335
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.334
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.333
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.332
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.331
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.330
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.329
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.328
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.327
2 findingsThis version was published by a different npm account than previous versions on 2026-04-28. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.326
2 findingsThis version was published by a different npm account than previous versions on 2026-04-22. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.325
2 findingsThis version was published by a different npm account than previous versions on 2026-04-15. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.324
2 findingsThis version was published by a different npm account than previous versions on 2026-04-15. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.323
2 findingsThis version was published by a different npm account than previous versions on 2026-04-06. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.322
2 findingsThis version was published by a different npm account than previous versions on 2026-04-02. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.321
2 findingsThis version was published by a different npm account than previous versions on 2026-04-01. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.