@starasia/alert
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): Publisher has strong approval history; no other risk signals; likely a CI environment change rather than a supply-chain concern. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 4.2.0 | 0 / 8 | |
| 4.1.0 | 0 / 8 | |
| 4.0.1 | 0 / 8 | |
| 4.0.0 | 0 / 8 | |
| 3.0.0 | 0 / 8 | |
| 2.0.0 | 0 / 8 | |
| 1.0.8 | 0 / 8 | |
| 1.0.7 | 0 / 8 | |
| 1.0.6 | 0 / 8 | |
| 1.0.5 | 0 / 8 | |
| 1.0.1 | 0 / 10 | |
| 1.0.0 | 0 / 10 |
v4.2.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: rizkyizh.
v4.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: rizkyizh.