@mekari/pixel-accordion
Mekari Pixel | Accordion 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): Provenance attestation is rare; not a blocker for established packages. | ai | |
| license | weak-copyleft-license:LGPL-3.0 | AI (license): LGPL-3.0 is standard for this publisher's component library. | ai | |
| dependencies | unvetted-dep:@mekari/pixel-icon | AI (dependencies): Internal sibling package from same Mekari design system monorepo; expected dependency pattern. | ai | |
| dependencies | unvetted-dep:@mekari/pixel-utils | AI (dependencies): Internal sibling package from same Mekari design system monorepo; expected dependency pattern. | ai | |
| dependencies | unvetted-dep:@mekari/pixel-collapse | AI (dependencies): Internal sibling package from same Mekari design system monorepo; expected dependency pattern. | ai | |
| dependencies | unvetted-dep:@mekari/pixel-pseudo-box | AI (dependencies): Internal sibling package from same Mekari design system monorepo; expected dependency pattern. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.4.36 | 4 / 1 | |
| 0.4.35 | 4 / 1 | |
| 0.4.34 | 4 / 1 | |
| 0.4.33 | 4 / 1 | |
| 0.4.32 | 4 / 1 |
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.