@mekari/pixel-tooltip
Mekari Pixel | Tooltip 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@popperjs/core | AI (dependencies): @popperjs/core is a widely-used, well-maintained positioning library; not a security risk. | ai | |
| dependencies | unvetted-dep:@mekari/pixel-box | AI (dependencies): Internal sibling component from the same Mekari Pixel design system; stable false positive. | ai | |
| dependencies | unvetted-dep:@mekari/pixel-utils | AI (dependencies): Internal sibling component from the same Mekari Pixel design system; stable false positive. | ai | |
| dependencies | unvetted-dep:@mekari/pixel-popper | AI (dependencies): Internal sibling component from the same Mekari Pixel design system; stable false positive. | ai | |
| dependencies | unvetted-dep:@mekari/pixel-fragment | AI (dependencies): Internal sibling component from the same Mekari Pixel design system; stable false positive. | ai | |
| dependencies | unvetted-dep:@mekari/pixel-provider | AI (dependencies): Internal sibling component from the same Mekari Pixel design system; stable false positive. | ai | |
| dependencies | unvetted-dep:@mekari/pixel-visually-hidden | AI (dependencies): Internal sibling component from the same Mekari Pixel design system; stable false positive. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 0.5.24 | 7 / 1 | |
| 0.5.23 | 7 / 1 | |
| 0.5.22 | 7 / 1 | |
| 0.5.21 | 7 / 1 | |
| 0.5.20 | 7 / 1 | |
| 0.5.19 | 7 / 1 | |
| 0.5.18 | 7 / 1 | |
| 0.5.17 | 7 / 1 | |
| 0.5.16 | 7 / 1 | |
| 0.5.15 | 7 / 1 | |
| 0.5.14 | 7 / 1 | |
| 0.5.13 | 7 / 1 | |
| 0.5.12 | 7 / 1 | |
| 0.5.11 | 7 / 1 | |
| 0.5.10 | 7 / 1 | |
| 0.5.9 | 7 / 1 | |
| 0.5.8 | 7 / 1 | |
| 0.5.7 | 7 / 1 | |
| 0.5.6 | 7 / 1 | |
| 0.5.5 | 7 / 1 | |
| 0.5.4 | 7 / 1 | |
| 0.5.3 | 7 / 1 | |
| 0.5.2 | 7 / 1 | |
| 0.5.1 | 7 / 1 | |
| 0.5.0 | 7 / 1 | |
| 0.4.2 | 5 / 1 | |
| 0.4.1 | 5 / 1 | |
| 0.4.0 | 5 / 1 | |
| 0.3.0 | 5 / 1 | |
| 0.2.2 | 5 / 1 | |
| 0.2.1 | 5 / 1 | |
| 0.2.0 | 5 / 1 | |
| 0.1.1 | 5 / 1 | |
| 0.1.0 | 5 / 1 | |
| 0.0.14 | 5 / 1 | |
| 0.0.13 | 5 / 1 | |
| 0.0.12 | 5 / 1 | |
| 0.0.11 | 5 / 1 | |
| 0.0.10 | 5 / 1 | |
| 0.0.9 | 5 / 1 | |
| 0.0.8 | 5 / 1 | |
| 0.0.7 | 5 / 1 | |
| 0.0.6 | 5 / 1 | |
| 0.0.5 | 5 / 1 | |
| 0.0.4 | 5 / 1 | |
| 0.0.3 | 5 / 1 | |
| 0.0.2 | 5 / 1 |
v0.5.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.