web3-eth-ens
2
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
luu-alexmpetrunicjdevcsgregthegreek
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:web3-eth-abi | AI (phantom-deps): web3-eth-abi is declared as a runtime dependency in package.json; phantom-dep flag is a false positive for this monorepo package where it may be used indirectly or in type definitions. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): The raw IP (127.0.0.1) appears only in JSDoc documentation examples showing how to connect to a local test node. This is a stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Mass-production signal reflects ChainSafe's web3.js monorepo publishing pattern (many web3-* packages). No keywords is trivial. Not indicative of spam or malice. | ai |
v4.4.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.4
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.