@mekari/pixel-button
Mekari Pixel | 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 — 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-box | AI (dependencies): First-party sibling component from the same Mekari design system org; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@mekari/pixel-icon | AI (dependencies): First-party sibling component from the same Mekari design system org; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@mekari/pixel-utils | AI (dependencies): First-party sibling component from the same Mekari design system org; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@mekari/pixel-spinner | AI (dependencies): First-party sibling component from the same Mekari design system org; not a third-party risk. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.2.37 | 4 / 5 | |
| 0.2.36 | 4 / 5 | |
| 0.2.35 | 4 / 5 | |
| 0.2.34 | 4 / 5 | |
| 0.2.33 | 4 / 5 |
v0.2.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.