@mekari/pixel-badge
Mekari Pixel | Presents users with short relevant information
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-icon | AI (dependencies): First-party Mekari design system dependency; stable pattern across all pixel-* packages. | ai | |
| dependencies | unvetted-dep:@mekari/pixel-utils | AI (dependencies): First-party Mekari design system dependency; stable pattern across all pixel-* packages. | ai | |
| dependencies | unvetted-dep:@mekari/pixel-pseudo-box | AI (dependencies): First-party Mekari design system dependency; stable pattern across all pixel-* packages. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.4.36 | 3 / 2 | |
| 0.4.35 | 3 / 2 | |
| 0.4.34 | 3 / 2 | |
| 0.4.33 | 3 / 2 | |
| 0.4.32 | 3 / 2 |
v0.4.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.