@mekari/pixel-date-picker
Mekari Pixel | Date picker 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): Internal Mekari design-system sibling package; same publisher org, stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@mekari/pixel-flex | AI (dependencies): Internal Mekari design-system sibling package; same publisher org, stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@mekari/pixel-text | AI (dependencies): Internal Mekari design-system sibling package; same publisher org, stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@mekari/pixel-utils | AI (dependencies): Internal Mekari design-system sibling package; same publisher org, stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@mekari/pixel-simple-grid | AI (dependencies): Internal Mekari design-system sibling package; same publisher org, stable pattern across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established Mekari org package; no provenance is consistent across all 74 versions and poses no incremental risk. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.12.26 | 11 / 1 | |
| 0.12.25 | 11 / 1 | |
| 0.12.24 | 11 / 1 | |
| 0.12.23 | 11 / 1 | |
| 0.12.22 | 11 / 1 | |
| 0.12.21 | 11 / 1 |
v0.12.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.22
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.12.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.