web3-utils
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Publisher change verified stable on npm for 897d, consistent with legitimate handoff. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Stale unremoved publish is evidence against takeover; long-standing established package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are well-known ethereum ecosystem libs replacing deprecated ethereumjs-util. | ai | |
| bogus-package | bogus-package | AI (bogus-package): web3-utils is a core utility package in the web3.js monorepo. The mass-production signal reflects ChainSafe's monorepo publishing pattern, not spam. No keywords is cosmetic. | ai | |
| dependencies | unvetted-dep:web3-validator | AI (dependencies): web3-validator is a sibling package in the web3.js monorepo (ChainSafe/web3.js); expected internal dependency, not a suspicious third-party package. | ai | |
| dependencies | unvetted-dep:web3-types | AI (dependencies): web3-types is a sibling package in the web3.js monorepo (ChainSafe/web3.js); expected internal dependency, not a suspicious third-party package. | ai | |
| dependencies | unvetted-dep:web3-errors | AI (dependencies): web3-errors is a sibling package in the web3.js monorepo (ChainSafe/web3.js); expected internal dependency, not a suspicious third-party package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 4.3.3 | 5 / 15 | |
| 4.3.2 | 5 / 15 | |
| 4.3.1 | 5 / 15 | |
| 4.3.0 | 5 / 15 | |
| 4.2.3 | 5 / 15 | |
| 4.2.2 | 5 / 15 | |
| 4.2.1 | 5 / 15 | |
| 4.0.0 | 1 / 10 | |
| 1.10.4 | 8 / 2 |
v4.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (luu-alex) than the most recent previously approved version (jdevcs) on 2024-05-23, but luu-alex is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (luu-alex) than the most recent previously approved version (jdevcs) on 2024-03-26, but luu-alex is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.4
2 findingsThis version was published by a different npm account (jdevcs) than the most recent previously approved version (spacesailor) on 2024-02-05. It has since remained available on npm for 897 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.