@snack-uikit/toggles
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
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.13.27 | 5 / 0 | |
| 0.13.26 | 5 / 0 | |
| 0.13.25 | 5 / 0 | |
| 0.13.24 | 5 / 0 | |
| 0.13.23 | 5 / 0 | |
| 0.13.22 | 5 / 0 | |
| 0.13.21 | 5 / 0 | |
| 0.13.20 | 5 / 0 | |
| 0.13.19 | 5 / 0 | |
| 0.13.18 | 5 / 0 | |
| 0.13.17 | 5 / 0 | |
| 0.13.16 | 5 / 0 | |
| 0.13.15 | 5 / 0 | |
| 0.13.14 | 5 / 0 |
v0.13.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.