web3-eth-accounts
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): Expected from major-version rewrite/monorepo split, not injected code. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Legit growth from v1→v4 rewrite with new modular deps. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Publisher stable 915d, high approval track record; not a takeover pattern. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Long-stable publish, no unpublish, consistent with legitimate transfer. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Established package with continuous downloads; dormancy explained by prior gap, no malicious content found. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Standard hex-to-buffer conversion for tx signing, not payload hiding. | ai | |
| dependencies | unvetted-dep:scrypt-js | AI (dependencies): Well-known, widely used crypto KDF library, standard for Ethereum key handling. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Localhost URL in a JSDoc example comment, not executed. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Official ChainSafe web3.js monorepo package; templated-name/no-keyword heuristic is a stable FP here. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 4.3.1 | 7 / 14 | |
| 4.3.0 | 7 / 14 | |
| 4.2.1 | 7 / 14 | |
| 4.2.0 | 7 / 14 | |
| 4.1.3 | 7 / 14 | |
| 4.1.2 | 7 / 14 | |
| 4.1.1 | 7 / 14 | |
| 4.1.0 | 7 / 14 | |
| 4.0.6 | 7 / 14 | |
| 4.0.5 | 7 / 14 | |
| 4.0.4 | 7 / 14 | |
| 4.0.3 | 7 / 14 | |
| 4.0.2 | 7 / 14 | |
| 4.0.1 | 7 / 14 | |
| 1.10.4 | 10 / 2 |
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.3
2 findings[Reject — re-review on republish] (prior reject: AI (bogus-package): Unknown publisher with mass-production pattern publishing a well-known package name is a persistent red flag across all versions from this publisher.) 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.1.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-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.1.1
2 findingsThis version was published by a different npm account (luu-alex) than the most recent previously approved version (jdevcs) 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.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
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.