@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, 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 |
|---|---|---|---|---|
| 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 65 of 65)
| 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 | |
| 0.6.44 | 9 / 1 | |
| 0.6.43 | 9 / 1 | |
| 0.6.42 | 9 / 1 | |
| 0.6.41 | 9 / 1 | |
| 0.6.40 | 9 / 1 | |
| 0.6.39 | 9 / 1 | |
| 0.6.38 | 9 / 1 | |
| 0.6.37 | 9 / 1 | |
| 0.6.36 | 9 / 1 | |
| 0.6.35 | 9 / 1 | |
| 0.6.34 | 9 / 1 | |
| 0.6.33 | 9 / 1 | |
| 0.6.32 | 9 / 1 | |
| 0.6.31 | 9 / 1 | |
| 0.6.30 | 9 / 1 | |
| 0.6.29 | 9 / 1 | |
| 0.6.28 | 9 / 1 | |
| 0.6.27 | 9 / 1 | |
| 0.6.26 | 9 / 1 | |
| 0.6.25 | 9 / 1 | |
| 0.6.24 | 9 / 1 | |
| 0.6.23 | 9 / 1 | |
| 0.6.22 | 9 / 1 | |
| 0.6.21 | 9 / 1 | |
| 0.6.20 | 9 / 1 | |
| 0.6.19 | 9 / 1 | |
| 0.6.18 | 9 / 1 | |
| 0.6.17 | 9 / 1 | |
| 0.6.16 | 9 / 1 | |
| 0.6.15 | 9 / 1 | |
| 0.6.14 | 9 / 1 | |
| 0.6.13 | 9 / 1 | |
| 0.6.12 | 9 / 1 | |
| 0.6.11 | 9 / 1 | |
| 0.6.10 | 9 / 1 | |
| 0.6.9 | 9 / 1 | |
| 0.6.8 | 9 / 1 | |
| 0.6.7 | 9 / 1 | |
| 0.6.6 | 9 / 1 | |
| 0.6.5 | 9 / 1 | |
| 0.6.4 | 9 / 1 | |
| 0.6.3 | 9 / 1 | |
| 0.6.2 | 9 / 1 | |
| 0.6.1 | 9 / 1 | |
| 0.6.0 | 9 / 1 | |
| 0.5.0 | 9 / 1 | |
| 0.4.2 | 9 / 1 | |
| 0.4.1 | 9 / 1 | |
| 0.4.0 | 9 / 1 | |
| 0.3.0 | 9 / 1 | |
| 0.2.5 | 5 / 1 | |
| 0.2.4 | 5 / 1 | |
| 0.2.3 | 5 / 1 | |
| 0.2.2 | 5 / 1 | |
| 0.2.1 | 5 / 1 | |
| 0.2.0 | 5 / 1 | |
| 0.1.3 | 5 / 1 | |
| 0.1.2 | 5 / 1 | |
| 0.1.1 | 5 / 1 |
v0.6.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.30
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.29
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.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
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.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
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.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.