@mekari/pixel-airene-button
Mekari Pixel | Airene button component
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 | no-provenance | AI (provenance): Mekari org packages consistently lack Sigstore provenance; stable false positive for this publisher. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.1.11 | 5 / 2 | |
| 0.1.10 | 5 / 2 | |
| 0.1.9 | 5 / 2 | |
| 0.1.8 | 5 / 2 | |
| 0.1.7 | 5 / 2 | |
| 0.1.6 | 5 / 2 | |
| 0.1.5 | 5 / 2 | |
| 0.1.4 | 5 / 2 | |
| 0.1.3 | 5 / 2 | |
| 0.1.2 | 5 / 2 | |
| 0.1.1 | 5 / 2 | |
| 0.1.0 | 5 / 2 |
v0.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
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.