web3-bzz
2
Versions
—
License
Yes
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-alexmpetrunicjdevcsgregthegreekholgerd77
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall is a harmless echo deprecation warning; no code execution or network access. Stable pattern for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Mass-production signal reflects the web3.js monorepo pattern (many web3-* packages); not spam. No keywords is minor for an established ecosystem package. | ai |
v1.10.4
2 findings
HIGH
Package has 'postinstall' script
install-scripts
Script: echo "WARNING: the web3-bzz api will be deprecated in the next version"
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.3
2 findings
HIGH
Package has 'postinstall' script
install-scripts
Script: echo "WARNING: the web3-bzz api will be deprecated in the next version"
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.