@exodus/asset-types
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): publishConfig explicitly sets provenance:false; stable org decision across versions. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.10.0 | 0 / 4 | |
| 0.9.0 | 0 / 4 | |
| 0.8.0 | 3 / 1 | |
| 0.7.1 | 3 / 1 | |
| 0.7.0 | 3 / 1 | |
| 0.6.0 | 3 / 1 | |
| 0.5.1 | 3 / 1 | |
| 0.5.0 | 3 / 1 | |
| 0.4.0 | 3 / 1 | |
| 0.3.1 | 3 / 1 | |
| 0.3.0 | 3 / 1 | |
| 0.2.4 | 3 / 1 | |
| 0.2.3 | 3 / 1 | |
| 0.2.2 | 3 / 1 | |
| 0.2.1 | 3 / 1 | |
| 0.2.0 | 3 / 1 | |
| 0.1.0 | 3 / 0 |
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.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.