@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, so a manually published version cannot be tied back to a reviewed commit.
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 51 of 69)
| Version | Deps | Published |
|---|---|---|
| 0.2.44 | 8 / 4 | |
| 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 | |
| 0.2.37 | 8 / 4 | |
| 0.2.36 | 8 / 4 | |
| 0.2.35 | 8 / 4 | |
| 0.2.34 | 8 / 4 | |
| 0.2.33 | 8 / 4 | |
| 0.2.32 | 8 / 4 | |
| 0.2.31 | 8 / 4 | |
| 0.2.30 | 8 / 4 | |
| 0.2.29 | 8 / 4 | |
| 0.2.28 | 8 / 4 | |
| 0.2.27 | 8 / 4 | |
| 0.2.26 | 8 / 4 | |
| 0.2.25 | 8 / 4 | |
| 0.2.24 | 8 / 4 | |
| 0.2.23 | 8 / 4 | |
| 0.2.22 | 8 / 4 | |
| 0.2.21 | 8 / 4 | |
| 0.2.20 | 8 / 4 | |
| 0.2.19 | 8 / 4 | |
| 0.2.18 | 6 / 4 | |
| 0.2.17 | 6 / 4 | |
| 0.2.16 | 6 / 4 | |
| 0.2.15 | 6 / 4 | |
| 0.2.14 | 6 / 4 | |
| 0.2.13 | 6 / 4 | |
| 0.2.12 | 6 / 4 | |
| 0.2.11 | 6 / 4 | |
| 0.2.10 | 6 / 4 | |
| 0.2.9 | 6 / 4 | |
| 0.2.8 | 6 / 4 | |
| 0.2.7 | 6 / 4 | |
| 0.2.6 | 6 / 4 | |
| 0.2.5 | 6 / 4 | |
| 0.2.4 | 6 / 4 | |
| 0.2.3 | 6 / 4 | |
| 0.2.2 | 6 / 4 | |
| 0.2.1 | 6 / 4 | |
| 0.2.0 | 6 / 4 | |
| 0.1.0 | 6 / 4 | |
| 0.0.24 | 6 / 4 | |
| 0.0.23 | 6 / 4 | |
| 0.0.22 | 6 / 4 | |
| 0.0.21 | 6 / 4 | |
| 0.0.20 | 6 / 4 |
v0.2.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.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.2.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.