@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, 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): 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 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 0.4.37 | 4 / 1 | |
| 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 | |
| 0.4.31 | 4 / 1 | |
| 0.4.30 | 4 / 1 | |
| 0.4.29 | 4 / 1 | |
| 0.4.28 | 4 / 1 | |
| 0.4.27 | 4 / 1 | |
| 0.4.26 | 4 / 1 | |
| 0.4.25 | 4 / 1 | |
| 0.4.24 | 4 / 1 | |
| 0.4.23 | 4 / 1 | |
| 0.4.22 | 4 / 1 | |
| 0.4.21 | 4 / 1 | |
| 0.4.20 | 4 / 1 | |
| 0.4.19 | 4 / 1 | |
| 0.4.18 | 4 / 1 | |
| 0.4.17 | 4 / 1 | |
| 0.4.16 | 4 / 1 | |
| 0.4.15 | 4 / 1 | |
| 0.4.14 | 4 / 1 | |
| 0.4.13 | 4 / 1 | |
| 0.4.12 | 4 / 1 | |
| 0.4.11 | 4 / 1 | |
| 0.4.10 | 4 / 1 | |
| 0.4.9 | 4 / 1 | |
| 0.4.8 | 4 / 1 | |
| 0.4.7 | 4 / 1 | |
| 0.4.6 | 4 / 1 | |
| 0.4.5 | 4 / 1 | |
| 0.4.4 | 4 / 1 | |
| 0.4.3 | 4 / 1 | |
| 0.4.2 | 4 / 1 | |
| 0.4.1 | 4 / 1 | |
| 0.4.0 | 4 / 1 | |
| 0.3.0 | 4 / 1 | |
| 0.2.1 | 4 / 1 | |
| 0.2.0 | 4 / 1 | |
| 0.1.9 | 4 / 1 | |
| 0.1.8 | 4 / 1 | |
| 0.1.7 | 4 / 1 | |
| 0.1.6 | 4 / 1 | |
| 0.1.5 | 4 / 1 | |
| 0.1.4 | 4 / 1 | |
| 0.1.3 | 4 / 1 | |
| 0.1.2 | 4 / 1 | |
| 0.1.1 | 4 / 1 | |
| 0.1.0 | 4 / 1 |
v0.4.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.19
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.4.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
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.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.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
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. Consider requesting the maintainer enable provenance via CI/CD.
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.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.