@snack-uikit/popover-private
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:@snack-uikit/utils | AI (dependencies): Sibling package from the same snack-uikit monorepo; not an independent risk. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.15.6 | 5 / 1 | |
| 0.15.5 | 5 / 1 | |
| 0.15.4 | 5 / 1 | |
| 0.15.3 | 5 / 1 | |
| 0.15.2 | 5 / 1 | |
| 0.15.1 | 5 / 1 | |
| 0.15.0 | 5 / 1 | |
| 0.14.8 | 5 / 1 |
v0.15.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.