@snack-uikit/toolbar
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): Consistent across all @snack-uikit/* packages; publisher has clean track record. | ai |
Versions (showing 100 of 132)
| Version | Deps | Published |
|---|---|---|
| 0.14.29 | 12 / 0 | |
| 0.14.28 | 12 / 0 | |
| 0.14.27 | 12 / 0 | |
| 0.14.26 | 12 / 0 | |
| 0.14.25 | 12 / 0 | |
| 0.14.24 | 12 / 0 | |
| 0.14.23 | 12 / 0 | |
| 0.14.22 | 12 / 0 | |
| 0.14.21 | 12 / 0 | |
| 0.14.20 | 12 / 0 | |
| 0.14.19 | 12 / 0 | |
| 0.14.18 | 12 / 0 | |
| 0.14.17 | 12 / 0 | |
| 0.14.16 | 12 / 0 | |
| 0.14.15 | 12 / 0 | |
| 0.14.14 | 12 / 0 | |
| 0.14.13 | 12 / 0 | |
| 0.14.12 | 12 / 0 | |
| 0.14.11 | 12 / 0 | |
| 0.14.10 | 12 / 0 | |
| 0.14.9 | 12 / 0 | |
| 0.14.8 | 12 / 0 | |
| 0.14.7 | 12 / 0 | |
| 0.14.6 | 12 / 0 | |
| 0.14.5 | 12 / 0 | |
| 0.14.4 | 12 / 0 | |
| 0.14.3 | 12 / 0 | |
| 0.14.2 | 12 / 0 | |
| 0.14.1 | 12 / 0 | |
| 0.14.0 | 12 / 0 | |
| 0.13.23 | 11 / 0 | |
| 0.13.22 | 11 / 0 | |
| 0.13.21 | 11 / 0 | |
| 0.13.20 | 11 / 0 | |
| 0.13.19 | 11 / 0 | |
| 0.13.18 | 11 / 0 | |
| 0.13.17 | 11 / 0 | |
| 0.13.16 | 11 / 0 | |
| 0.13.15 | 11 / 0 | |
| 0.13.14 | 11 / 0 | |
| 0.13.13 | 11 / 0 | |
| 0.13.12 | 11 / 0 | |
| 0.13.11 | 11 / 0 | |
| 0.13.10 | 11 / 0 | |
| 0.13.9 | 11 / 0 | |
| 0.13.8 | 11 / 0 | |
| 0.13.7 | 11 / 0 | |
| 0.13.6 | 11 / 0 | |
| 0.13.5 | 11 / 0 | |
| 0.13.4 | 11 / 0 | |
| 0.13.3 | 11 / 0 | |
| 0.13.2 | 11 / 0 | |
| 0.13.1 | 11 / 0 | |
| 0.13.0 | 11 / 0 | |
| 0.12.13 | 11 / 0 | |
| 0.12.12 | 11 / 0 | |
| 0.12.11 | 11 / 0 | |
| 0.12.10 | 11 / 0 | |
| 0.12.9 | 11 / 0 | |
| 0.12.8 | 11 / 0 | |
| 0.12.7 | 11 / 0 | |
| 0.12.6 | 11 / 0 | |
| 0.12.5 | 11 / 0 | |
| 0.12.4 | 11 / 0 | |
| 0.12.3 | 11 / 0 | |
| 0.12.2 | 11 / 0 | |
| 0.12.1 | 11 / 0 | |
| 0.12.0 | 11 / 0 | |
| 0.11.8 | 11 / 0 | |
| 0.11.7 | 11 / 0 | |
| 0.11.6 | 11 / 0 | |
| 0.11.5 | 11 / 0 | |
| 0.11.4 | 11 / 0 | |
| 0.11.3 | 11 / 0 | |
| 0.11.2 | 11 / 0 | |
| 0.11.1 | 11 / 0 | |
| 0.11.0 | 11 / 0 | |
| 0.10.3 | 9 / 0 | |
| 0.10.2 | 9 / 0 | |
| 0.10.1 | 9 / 0 | |
| 0.10.0 | 9 / 0 | |
| 0.9.18 | 8 / 0 | |
| 0.9.17 | 8 / 0 | |
| 0.9.16 | 8 / 0 | |
| 0.9.15 | 8 / 0 | |
| 0.9.14 | 8 / 0 | |
| 0.9.13 | 8 / 0 | |
| 0.9.12 | 8 / 0 | |
| 0.9.11 | 8 / 0 | |
| 0.9.10 | 8 / 0 | |
| 0.9.9 | 8 / 0 | |
| 0.9.8 | 8 / 0 | |
| 0.9.7 | 8 / 0 | |
| 0.9.6 | 8 / 0 | |
| 0.9.5 | 8 / 0 | |
| 0.9.4 | 8 / 0 | |
| 0.9.3 | 8 / 0 | |
| 0.9.2 | 8 / 0 | |
| 0.9.1 | 8 / 0 | |
| 0.9.0 | 8 / 0 |
v0.14.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.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.
v0.12.13
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.12.12
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.12.11
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.12.10
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.12.9
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.12.8
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.12.7
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.12.6
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.12.5
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.12.4
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.12.3
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.12.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.12.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.12.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.
v0.11.8
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.11.7
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.11.6
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.11.5
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.11.4
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.11.3
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.11.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.11.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.11.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.
v0.10.3
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.10.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.10.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.10.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.
v0.9.18
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.9.17
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.9.16
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.9.15
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.9.14
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.9.13
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.9.12
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.9.11
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.9.10
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.9.9
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.9.8
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.9.7
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.9.6
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.9.5
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.9.4
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.9.3
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.9.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.9.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.9.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.