@exodus/models
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:proxy-freeze | AI (dependencies): Small utility dep used by established Exodus package; no malicious indicators. | ai | |
| dependencies | unvetted-dep:minimalistic-assert | AI (dependencies): Widely used assertion utility; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Exodus org explicitly sets provenance:false in publishConfig; consistent across their packages. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 13.3.1 | 6 / 3 | |
| 13.3.0 | 6 / 3 | |
| 13.2.5 | 6 / 3 | |
| 13.2.4 | 6 / 3 | |
| 13.2.3 | 6 / 3 | |
| 13.2.2 | 6 / 3 | |
| 13.2.1 | 6 / 3 | |
| 13.2.0 | 6 / 3 | |
| 13.1.5 | 6 / 3 | |
| 13.1.4 | 6 / 3 | |
| 13.1.3 | 6 / 3 | |
| 13.1.2 | 6 / 3 | |
| 13.1.1 | 6 / 3 | |
| 13.1.0 | 6 / 3 | |
| 13.0.0 | 6 / 3 | |
| 12.19.1 | 6 / 3 | |
| 12.19.0 | 6 / 3 |
v13.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.2.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.
v13.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.1.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.
v13.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.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.
v12.19.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.19.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.