@mekari/pixel-button-icon
Mekari Pixel | Displays a single less important action a user can take 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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@mekari/pixel-utils | AI (dependencies): Internal Mekari org dependency; consistent with the package's established ecosystem of sibling @mekari/pixel-* packages. | ai | |
| provenance | no-provenance | AI (provenance): Established Mekari org package; no provenance is consistent across all 59 versions and poses no direct risk. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.8.37 | 3 / 2 | |
| 0.8.36 | 3 / 2 | |
| 0.8.35 | 3 / 2 | |
| 0.8.34 | 3 / 2 | |
| 0.8.33 | 3 / 2 |
v0.8.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.