@starasia/menu
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): No other risk signals; likely a CI environment change, not a supply-chain concern for this package. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 3.6.2 | 0 / 10 | |
| 3.6.1 | 0 / 10 | |
| 3.6.0 | 0 / 10 | |
| 3.5.0 | 0 / 10 | |
| 3.4.0 | 0 / 10 | |
| 3.3.3 | 0 / 10 | |
| 3.3.2 | 0 / 10 | |
| 3.3.1 | 0 / 10 | |
| 3.3.0 | 0 / 10 | |
| 3.2.0 | 0 / 10 | |
| 3.1.0 | 0 / 10 | |
| 3.0.0 | 0 / 10 | |
| 2.0.1 | 0 / 10 | |
| 2.0.0 | 0 / 10 | |
| 1.0.3 | 0 / 10 | |
| 1.0.2 | 0 / 10 | |
| 1.0.1 | 0 / 10 | |
| 1.0.0 | 0 / 10 |
v3.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.