@exodus/assets
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 | dormant-publish | AI (publish-pattern): Exodus org package with consistent metadata and CI publisher; dormancy likely reflects org release cadence, not takeover. | ai | |
| dependencies | unvetted-dep:minimalistic-assert | AI (dependencies): minimalistic-assert is a well-known, stable utility; no security concerns for this package. | ai | |
| provenance | no-provenance | AI (provenance): Exodus org explicitly sets provenance:false in publishConfig; stable pattern across their packages. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 11.10.0 | 7 / 5 | |
| 11.9.0 | 7 / 5 | |
| 11.8.0 | 7 / 5 | |
| 11.7.0 | 7 / 5 | |
| 11.6.0 | 7 / 5 | |
| 11.5.0 | 7 / 5 | |
| 11.4.0 | 7 / 5 | |
| 11.3.2 | 7 / 5 | |
| 11.3.1 | 7 / 5 | |
| 11.3.0 | 7 / 5 | |
| 11.2.0 | 7 / 5 | |
| 11.1.5 | 7 / 5 | |
| 11.1.4 | 7 / 5 | |
| 11.1.3 | 7 / 5 | |
| 11.1.2 | 7 / 4 | |
| 11.1.1 | 7 / 2 | |
| 11.1.0 | 7 / 2 | |
| 11.0.1 | 5 / 2 | |
| 11.0.0 | 5 / 2 |
v11.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.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.