@mekari/pixel-upload
Mekari Pixel | Upload 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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package with long history; provenance absence is common and not a disqualifier here. | ai | |
| dependencies | unvetted-dep:@mekari/pixel-box | AI (dependencies): Internal Mekari design system sibling package; stable false positive for this org's packages. | ai | |
| dependencies | unvetted-dep:@mekari/pixel-flex | AI (dependencies): Internal Mekari design system sibling package; stable false positive for this org's packages. | ai | |
| dependencies | unvetted-dep:@mekari/pixel-text | AI (dependencies): Internal Mekari design system sibling package; stable false positive for this org's packages. | ai | |
| dependencies | unvetted-dep:@mekari/pixel-utils | AI (dependencies): Internal Mekari design system sibling package; stable false positive for this org's packages. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.6.50 | 9 / 1 | |
| 0.6.49 | 9 / 1 | |
| 0.6.48 | 9 / 1 | |
| 0.6.47 | 9 / 1 | |
| 0.6.46 | 9 / 1 | |
| 0.6.45 | 9 / 1 |
v0.6.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.47
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.6.46
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.6.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.