web3-eth-contract
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-alexmpetrunicgregthegreekjdevcs
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/bn.js | AI (phantom-deps): @types/bn.js is intentionally declared as a runtime dep in web3-eth-contract for TypeScript consumers; this is a stable pattern in the web3.js monorepo. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): 127.0.0.1 appears only in JSDoc documentation examples showing local test node usage (Ganache/Hardhat). Not an actual network request; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Mass-production signal reflects the web3.js monorepo pattern (many web3-* packages). No-keywords is minor. Both are false positives for this established ecosystem package. | ai |
v4.7.2
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.