web3
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | net-exec-file:dist/web3.min.js | AI (source-diff): Webpack browser bundle of the Ethereum API; network+eval are normal library features, not a payload. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size jump is the minified browser bundle being (re)added; stable for this package. | ai | |
| source-diff | encoded-string-file:dist/web3.min.js | AI (source-diff): Minified webpack bundle output (RLP encoding logic), not obfuscation; stable for this package. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall is just an echo statement advertising web3 4.x; no code execution. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 4.16.0 | 17 / 20 | |
| 4.15.0 | 17 / 20 | |
| 4.14.0 | 17 / 20 | |
| 4.13.0 | 17 / 20 | |
| 4.12.1 | 17 / 20 | |
| 4.12.0 | 17 / 20 | |
| 4.11.1 | 17 / 20 | |
| 4.11.0 | 17 / 20 | |
| 4.10.0 | 17 / 20 | |
| 4.9.0 | 16 / 20 | |
| 4.8.0 | 16 / 20 | |
| 4.7.0 | 16 / 20 | |
| 4.6.0 | 16 / 20 | |
| 4.5.0 | 16 / 20 | |
| 4.4.0 | 16 / 20 | |
| 4.3.0 | 16 / 18 | |
| 4.2.2 | 16 / 18 | |
| 4.2.1 | 16 / 18 | |
| 4.2.0 | 16 / 18 | |
| 4.1.2 | 16 / 17 | |
| 4.1.1 | 16 / 17 | |
| 4.1.0 | 16 / 17 | |
| 4.0.3 | 16 / 17 | |
| 4.0.2 | 16 / 17 | |
| 4.0.1 | 16 / 17 | |
| 1.10.4 | 7 / 4 |
v4.15.0
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.14.0
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.0
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.1
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.0
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (jdevcs) than the most recent previously approved version (luu-alex) on 2024-08-22, but jdevcs 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.11.1
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.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-07-11, 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.10.0
3 findingsModified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package 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-06-17, 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.9.0
3 findingsModified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package 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.8.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.7.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-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.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 (jdevcs) than the most recent previously approved version (luu-alex) on 2024-03-08, but jdevcs 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
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-02-12, 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.4.0
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. 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 (jdevcs) than the most recent previously approved version (luu-alex) on 2023-11-03, but jdevcs 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
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 2023-10-25, 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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage 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.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.