@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, 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 |
|---|---|---|---|---|
| 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 26 of 328)
| Version | Deps | Published |
|---|---|---|
| 0.0.72 | 1 / 2 | |
| 0.0.71 | 1 / 2 | |
| 0.0.70 | 1 / 2 | |
| 0.0.69 | 1 / 2 | |
| 0.0.68 | 1 / 2 | |
| 0.0.67 | 1 / 2 | |
| 0.0.66 | 1 / 2 | |
| 0.0.65 | 1 / 2 | |
| 0.0.64 | 1 / 2 | |
| 0.0.63 | 1 / 2 | |
| 0.0.62 | 1 / 2 | |
| 0.0.61 | 1 / 2 | |
| 0.0.60 | 1 / 2 | |
| 0.0.59 | 1 / 2 | |
| 0.0.58 | 1 / 2 | |
| 0.0.57 | 1 / 2 | |
| 0.0.56 | 1 / 2 | |
| 0.0.55 | 1 / 2 | |
| 0.0.54 | 1 / 2 | |
| 0.0.53 | 1 / 2 | |
| 0.0.52 | 1 / 2 | |
| 0.0.51 | 1 / 2 | |
| 0.0.50 | 1 / 2 | |
| 0.0.49 | 1 / 2 | |
| 0.0.48 | 1 / 2 | |
| 0.0.1 | 1 / 2 |
v0.0.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.