@exodus/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-removed | AI (maintainer-change): Large org-wide maintainer list trim, not a takeover; repo/deps unchanged. | ai | |
| provenance | publisher-changed | AI (provenance): Switch to GitHub Actions CI publisher is a positive provenance shift, not compromise. | ai | |
| provenance | no-provenance | AI (provenance): Exodus org packages consistently lack provenance; stable false positive for this publisher. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1.53.0 | 3 / 5 | |
| 1.52.0 | 3 / 5 | |
| 1.51.2 | 3 / 2 | |
| 1.51.1 | 3 / 1 | |
| 1.51.0 | 3 / 1 | |
| 1.50.1 | 3 / 1 | |
| 1.50.0 | 3 / 1 | |
| 1.49.0 | 3 / 1 | |
| 1.48.3 | 3 / 1 | |
| 1.48.2 | 3 / 1 | |
| 1.48.1 | 3 / 1 | |
| 1.48.0 | 3 / 1 | |
| 1.47.1 | 3 / 1 | |
| 1.47.0 | 3 / 1 | |
| 1.46.0 | 3 / 1 | |
| 1.45.0 | 3 / 1 | |
| 1.44.0 | 3 / 1 | |
| 1.43.1 | 3 / 1 |
v1.53.0
2 findingsThis version was published by a different npm account than previous versions on 2026-07-14. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.52.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-05-27. This could indicate a legitimate maintainer transition or an account compromise.
v1.51.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.51.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.50.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.49.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (joshuabot) than the most recent previously approved version (bulgakovk) on 2025-01-21, but joshuabot 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.
v1.48.3
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (joshuabot) than the most recent previously approved version (bulgakovk) on 2024-12-23, but joshuabot 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.
v1.48.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.48.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (lanahizzle) than the most recent previously approved version (bulgakovk) on 2024-09-13, but lanahizzle 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.
v1.48.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.47.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.47.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.46.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.45.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.44.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.43.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.