@mekari/pixel-tag
Mekari Pixel | Tag component is used for items that need to be labeled categorized or organized using keywords that describe them 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-icon | AI (dependencies): Internal Mekari design system dependency; expected for this component package. | ai | |
| dependencies | unvetted-dep:@mekari/pixel-utils | AI (dependencies): Internal Mekari design system dependency; expected for this component package. | ai | |
| dependencies | unvetted-dep:@mekari/pixel-pseudo-box | AI (dependencies): Internal Mekari design system dependency; expected for this component package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.6.35 | 3 / 2 | |
| 0.6.34 | 3 / 2 | |
| 0.6.33 | 3 / 2 | |
| 0.6.32 | 3 / 2 | |
| 0.6.31 | 3 / 2 |
v0.6.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.