@mekari/pixel-nuxt
Nuxt Module for Pixel Next
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-mask | AI (dependencies): Internal Mekari/Pixel monorepo sibling; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@mekari/pixel-theme | AI (dependencies): Internal Mekari/Pixel monorepo sibling; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@mekari/pixel-utils | AI (dependencies): Internal Mekari/Pixel monorepo sibling; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@mekari/pixel-directive | AI (dependencies): Internal Mekari/Pixel monorepo sibling; stable false positive for this package family. | ai | |
| license | weak-copyleft-license:LGPL-3.0 | AI (license): Package intentionally licensed LGPL-3.0; stable across all versions. | ai | |
| provenance | no-provenance | AI (provenance): Established org package; lack of Sigstore provenance is consistent across all 73 versions and not a meaningful risk signal here. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.2.43 | 8 / 4 | |
| 0.2.42 | 8 / 4 | |
| 0.2.41 | 8 / 4 | |
| 0.2.40 | 8 / 4 | |
| 0.2.39 | 8 / 4 | |
| 0.2.38 | 8 / 4 |
v0.2.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.41
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.2.40
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.2.39
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.2.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.