@panneau/lists
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Long-lived monorepo package; empty description is a cosmetic issue, not a risk signal. | ai | |
| provenance | no-provenance | AI (provenance): Established package predating Sigstore provenance adoption; absence is expected here. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 4.0.78 | 4 / 2 | |
| 4.0.75 | 4 / 2 | |
| 4.0.74 | 4 / 2 | |
| 4.0.73 | 4 / 2 | |
| 4.0.72 | 4 / 2 | |
| 4.0.68 | 4 / 2 | |
| 4.0.66 | 4 / 2 | |
| 4.0.65 | 4 / 2 | |
| 4.0.62 | 4 / 2 | |
| 4.0.58 | 4 / 2 | |
| 4.0.56 | 4 / 2 | |
| 4.0.55 | 4 / 2 | |
| 4.0.50 | 4 / 2 | |
| 4.0.48 | 4 / 2 | |
| 4.0.41 | 4 / 2 | |
| 4.0.39 | 4 / 2 | |
| 4.0.34 | 4 / 2 | |
| 4.0.33 | 4 / 2 | |
| 4.0.31 | 4 / 2 | |
| 4.0.27 | 4 / 2 | |
| 4.0.23 | 4 / 2 | |
| 4.0.21 | 4 / 2 | |
| 4.0.20 | 4 / 2 | |
| 4.0.19 | 4 / 2 | |
| 4.0.18 | 4 / 2 | |
| 4.0.17 | 4 / 2 | |
| 4.0.8 | 5 / 2 | |
| 4.0.7 | 5 / 2 | |
| 4.0.6 | 5 / 2 | |
| 4.0.5 | 5 / 2 | |
| 4.0.4 | 5 / 2 | |
| 4.0.2 | 5 / 2 | |
| 4.0.1 | 5 / 2 | |
| 4.0.0 | 5 / 2 | |
| 3.0.314 | 5 / 2 | |
| 3.0.308 | 5 / 2 | |
| 3.0.307 | 5 / 2 |
v4.0.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.