@acusti/use-is-out-of-bounds
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): Established package from known author; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.15.0 | 1 / 8 | |
| 0.14.1 | 1 / 5 | |
| 0.14.0 | 1 / 5 | |
| 0.13.1 | 1 / 5 | |
| 0.13.0 | 1 / 5 | |
| 0.12.0 | 1 / 5 | |
| 0.11.0 | 1 / 5 | |
| 0.10.0 | 1 / 5 |
v0.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.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.