web3-core
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are official web3-* sibling packages from same monorepo, not third-party. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Reflects known v1→v4 web3.js modular rewrite, not bundled payload. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Expected from major version restructuring of the monorepo package. | ai | |
| phantom-deps | phantom-dep:web3-providers-ipc | AI (phantom-deps): web3-providers-ipc is an optionalDependency loaded conditionally at runtime; phantom-dep is a false positive here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Signals are from monorepo structure (many web3-* packages under one maintainer) and missing keywords; not spam. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 4.7.1 | 9 / 14 | |
| 4.7.0 | 9 / 14 | |
| 4.6.0 | 9 / 14 | |
| 4.5.1 | 9 / 14 | |
| 4.5.0 | 9 / 14 | |
| 4.4.0 | 9 / 14 | |
| 4.3.2 | 9 / 14 | |
| 4.3.1 | 8 / 14 | |
| 4.3.0 | 8 / 14 | |
| 4.2.0 | 8 / 14 | |
| 4.1.1 | 8 / 14 | |
| 4.1.0 | 8 / 14 | |
| 4.0.3 | 8 / 14 | |
| 4.0.2 | 8 / 14 | |
| 4.0.1 | 8 / 14 | |
| 1.10.4 | 7 / 2 |
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-10-21, 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 (luu-alex) than the most recent previously approved version (jdevcs) on 2024-09-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.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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-06-13, 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
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.3.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 2023-12-04, 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.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. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
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.