@snack-uikit/button
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): Org-published monorepo package; no provenance is consistent across all versions. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 0.19.19 | 4 / 0 | |
| 0.19.18 | 4 / 0 | |
| 0.19.17 | 4 / 0 | |
| 0.19.16 | 4 / 0 | |
| 0.19.15 | 4 / 0 | |
| 0.19.14 | 4 / 0 | |
| 0.19.13 | 4 / 0 | |
| 0.19.12 | 4 / 0 | |
| 0.19.11 | 4 / 0 | |
| 0.19.10 | 4 / 0 | |
| 0.19.9 | 4 / 0 | |
| 0.19.8 | 4 / 0 | |
| 0.19.7 | 4 / 0 | |
| 0.19.6 | 4 / 0 | |
| 0.19.5 | 4 / 0 | |
| 0.19.4 | 4 / 0 | |
| 0.19.3 | 4 / 0 | |
| 0.19.2 | 4 / 0 | |
| 0.19.1 | 4 / 0 | |
| 0.19.0 | 4 / 0 | |
| 0.18.0 | 4 / 0 | |
| 0.17.5 | 4 / 0 | |
| 0.17.4 | 4 / 0 | |
| 0.17.3 | 4 / 0 | |
| 0.17.2 | 4 / 0 | |
| 0.17.1 | 4 / 0 | |
| 0.17.0 | 4 / 0 | |
| 0.16.1 | 4 / 0 | |
| 0.16.0 | 4 / 0 | |
| 0.15.1 | 4 / 0 | |
| 0.15.0 | 4 / 0 | |
| 0.14.1 | 4 / 0 | |
| 0.14.0 | 4 / 0 |
v0.19.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.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.17.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.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.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.14.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.