@snack-uikit/color-picker
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:@snack-uikit/segmented-control | AI (dependencies): Same-org monorepo sibling dependency; consistently safe pattern for this package family. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Intentionally empty description; consistent across this monorepo's packages. | ai |
Versions (showing 63 of 63)
| Version | Deps | Published |
|---|---|---|
| 0.3.58 | 7 / 0 | |
| 0.3.57 | 7 / 0 | |
| 0.3.56 | 7 / 0 | |
| 0.3.55 | 7 / 0 | |
| 0.3.54 | 7 / 0 | |
| 0.3.53 | 7 / 0 | |
| 0.3.52 | 7 / 0 | |
| 0.3.51 | 7 / 0 | |
| 0.3.50 | 7 / 0 | |
| 0.3.49 | 7 / 0 | |
| 0.3.48 | 7 / 0 | |
| 0.3.47 | 7 / 0 | |
| 0.3.46 | 7 / 0 | |
| 0.3.45 | 7 / 0 | |
| 0.3.44 | 7 / 0 | |
| 0.3.43 | 7 / 0 | |
| 0.3.42 | 7 / 0 | |
| 0.3.41 | 7 / 0 | |
| 0.3.40 | 7 / 0 | |
| 0.3.39 | 7 / 0 | |
| 0.3.38 | 7 / 0 | |
| 0.3.37 | 7 / 0 | |
| 0.3.36 | 7 / 0 | |
| 0.3.35 | 7 / 0 | |
| 0.3.34 | 7 / 0 | |
| 0.3.33 | 7 / 0 | |
| 0.3.32 | 7 / 0 | |
| 0.3.31 | 7 / 0 | |
| 0.3.30 | 7 / 0 | |
| 0.3.29 | 7 / 0 | |
| 0.3.28 | 7 / 0 | |
| 0.3.27 | 7 / 0 | |
| 0.3.26 | 7 / 0 | |
| 0.3.25 | 7 / 0 | |
| 0.3.24 | 7 / 0 | |
| 0.3.23 | 7 / 0 | |
| 0.3.22 | 7 / 0 | |
| 0.3.21 | 7 / 0 | |
| 0.3.20 | 7 / 0 | |
| 0.3.19 | 7 / 0 | |
| 0.3.18 | 7 / 0 | |
| 0.3.17 | 7 / 0 | |
| 0.3.16 | 7 / 0 | |
| 0.3.15 | 7 / 0 | |
| 0.3.14 | 7 / 0 | |
| 0.3.13 | 7 / 0 | |
| 0.3.12 | 7 / 0 | |
| 0.3.11 | 7 / 0 | |
| 0.3.10 | 7 / 0 | |
| 0.3.9 | 7 / 0 | |
| 0.3.8 | 7 / 0 | |
| 0.3.7 | 7 / 0 | |
| 0.3.6 | 7 / 0 | |
| 0.3.5 | 7 / 0 | |
| 0.3.4 | 7 / 0 | |
| 0.3.3 | 7 / 0 | |
| 0.3.2 | 6 / 1 | |
| 0.3.1 | 6 / 1 | |
| 0.3.0 | 6 / 1 | |
| 0.2.0 | 6 / 1 | |
| 0.1.2 | 6 / 1 | |
| 0.1.1 | 6 / 1 | |
| 0.1.0 | 6 / 1 |
v0.3.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
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. Only ~12% of npm packages have provenance, so this is common but not ideal.