web3-eth
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 |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): Refactor split monorepo deps into this package; expected growth. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Reflects major version jump 1.x->4.x, not account takeover. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Expected from 1.x->4.x rewrite/restructure. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Same transfer event, no takeover indicators. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Historical maintainer transfer within ChainSafe org, stable for years. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): All new deps are first-party web3-* sibling packages from same monorepo. | ai | |
| phantom-deps | phantom-dep:web3-providers-ws | AI (phantom-deps): Provider referenced via config; standard in this monorepo. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Localhost IP inside a JSDoc example comment, not executed code. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established ChainSafe web3.js module; mass-production/no-keyword heuristic is a stable FP here. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 4.11.1 | 11 / 13 | |
| 4.11.0 | 11 / 13 | |
| 4.10.0 | 11 / 13 | |
| 4.9.0 | 11 / 13 | |
| 4.8.2 | 11 / 13 | |
| 4.8.1 | 11 / 13 | |
| 4.8.0 | 11 / 13 | |
| 4.7.0 | 11 / 13 | |
| 4.6.0 | 11 / 13 | |
| 4.5.0 | 11 / 13 | |
| 4.4.0 | 11 / 13 | |
| 4.3.1 | 11 / 13 | |
| 4.3.0 | 11 / 13 | |
| 4.2.0 | 11 / 13 | |
| 4.1.1 | 11 / 14 | |
| 4.1.0 | 11 / 14 | |
| 4.0.3 | 11 / 14 | |
| 4.0.2 | 11 / 14 | |
| 4.0.1 | 11 / 14 | |
| 4.0.0 | 2 / 10 | |
| 1.10.4 | 12 / 2 |
v4.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.0
2 findings[Reject — re-review on republish] (prior reject: AI (bogus-package): Mass-production publisher pattern combined with unknown publisher identity is a persistent red flag for this package regardless of version.) Matched 2 signal(s), weighted score 4: • [S_PUBLISHER_MASS_PRODUCTION] Maintainer 'gregthegreek' owns 28 packages, ≥70% share a templated name shape. • [S_NO_KEYWORDS] No keywords declared.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.6.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-04-18, 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.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
2 findingsThis version was published by a different npm account (luu-alex) than the most recent previously approved version (spacesailor) on 2024-01-17. It has since remained available on npm for 915 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.
v4.3.1
2 findingsThis version was published by a different npm account (luu-alex) than the most recent previously approved version (spacesailor) on 2023-10-25. It has since remained available on npm for 999 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.
v4.3.0
2 findingsThis version was published by a different npm account (jdevcs) than the most recent previously approved version (spacesailor) on 2023-10-18. It has since remained available on npm for 1007 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.
v4.2.0
2 findingsThis version was published by a different npm account (jdevcs) than the most recent previously approved version (spacesailor) on 2023-09-19. It has since remained available on npm for 1036 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.
v4.1.1
2 findingsThis version was published by a different npm account (jdevcs) than the most recent previously approved version (spacesailor) on 2023-08-21. It has since remained available on npm for 1064 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.
v4.1.0
2 findingsThis version was published by a different npm account (jdevcs) than the most recent previously approved version (spacesailor) on 2023-08-15. It has since remained available on npm for 1071 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.
v4.0.3
2 findingsThis version was published by a different npm account (jdevcs) than the most recent previously approved version (spacesailor) on 2023-07-11. It has since remained available on npm for 1105 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.
v4.0.2
2 findingsThis version was published by a different npm account (jdevcs) than the most recent previously approved version (spacesailor) on 2023-06-27. It has since remained available on npm for 1120 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.
v4.0.1
2 findingsThis version was published by a different npm account (jdevcs) than the most recent previously approved version (spacesailor) on 2023-06-07. It has since remained available on npm for 1140 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.
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
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.