@exodus/asset-lib
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): ExodusMovement migrated publishing to GitHub Actions CI; consistent with publishConfig and org-wide pattern. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Mass maintainer removal consistent with org-level CI automation consolidation, not a takeover signal. | ai | |
| dependencies | unvetted-dep:minimalistic-assert | AI (dependencies): minimalistic-assert is a well-known, stable utility; stable dependency for this package. | ai | |
| provenance | no-provenance | AI (provenance): publishConfig explicitly sets provenance:false; stable pattern for this Exodus package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 5.9.1 | 9 / 2 | |
| 5.9.0 | 9 / 2 | |
| 5.8.1 | 9 / 2 | |
| 5.8.0 | 9 / 2 | |
| 5.7.0 | 9 / 2 | |
| 5.6.0 | 9 / 2 | |
| 5.5.0 | 9 / 2 | |
| 5.4.0 | 9 / 2 |
v5.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-05. 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.
v5.7.0
2 findingsThis version was published by a different npm account than previous versions on 2025-11-26. 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.
v5.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.