web3-eth-personal
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:web3-rpc-methods | AI (dependencies): First-party ChainSafe web3.js monorepo dependency; expected for this package. | ai | |
| dependencies | unvetted-dep:web3-types | AI (dependencies): First-party ChainSafe web3.js monorepo dependency; expected for this package. | ai | |
| dependencies | unvetted-dep:web3-validator | AI (dependencies): First-party ChainSafe web3.js monorepo dependency; expected for this package. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): 127.0.0.1:7545 is Ganache's localhost default used in JSDoc code examples throughout web3.js docs — not a real network endpoint or exfiltration target. | ai | |
| dependencies | unvetted-dep:web3-eth | AI (dependencies): First-party ChainSafe web3.js monorepo dependency; expected for this package. | ai | |
| dependencies | unvetted-dep:web3-core | AI (dependencies): First-party ChainSafe web3.js monorepo dependency; expected for this package. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node as a runtime dep is a known pattern in web3.js 1.x packages for TypeScript type resolution; not a real phantom dep concern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): web3.js monorepo produces many templated sub-packages by design; mass-production signal is a false positive for this ecosystem. | ai |
v4.1.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.