@mekari/pixel-color-picker
Mekari Pixel | Color picker let the user select a color
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Mekari Pixel component library does not use Sigstore provenance; stable pattern across the org. | ai | |
| phantom-deps | phantom-dep:@mekari/pixel-button-icon | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for monorepo component packages. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.0.18 | 12 / 1 | |
| 0.0.17 | 12 / 1 | |
| 0.0.16 | 12 / 1 | |
| 0.0.15 | 12 / 1 | |
| 0.0.14 | 12 / 1 | |
| 0.0.13 | 12 / 1 |
v0.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.16
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.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
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.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.