@snack-uikit/fields
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 versions of this package; publisher has 253 approved packages with no provenance issues. | ai | |
| dependencies | unvetted-dep:@snack-uikit/list | AI (dependencies): Same monorepo/publisher as parent; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@snack-uikit/slider | AI (dependencies): Same monorepo/publisher as parent; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@snack-uikit/tag | AI (dependencies): Same monorepo/publisher as parent; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@snack-uikit/skeleton | AI (dependencies): Same monorepo/publisher as parent; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@snack-uikit/color-picker | AI (dependencies): Same monorepo/publisher as parent; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@snack-uikit/calendar | AI (dependencies): Same monorepo/publisher as parent; stable false positive for this package family. | ai |
Versions (showing 100 of 209)
| Version | Deps | Published |
|---|---|---|
| 0.57.2 | 22 / 2 | |
| 0.57.1 | 22 / 2 | |
| 0.57.0 | 22 / 2 | |
| 0.56.2 | 22 / 2 | |
| 0.56.1 | 22 / 2 | |
| 0.56.0 | 22 / 2 | |
| 0.55.2 | 22 / 2 | |
| 0.55.1 | 22 / 2 | |
| 0.55.0 | 22 / 2 | |
| 0.53.1 | 22 / 2 | |
| 0.53.0 | 22 / 2 | |
| 0.51.17 | 22 / 2 | |
| 0.51.15 | 22 / 2 | |
| 0.51.13 | 22 / 2 | |
| 0.51.12 | 22 / 2 | |
| 0.51.7 | 22 / 2 | |
| 0.51.6 | 22 / 2 | |
| 0.51.5 | 22 / 2 | |
| 0.51.4 | 21 / 2 | |
| 0.51.3 | 21 / 2 | |
| 0.51.2 | 21 / 2 | |
| 0.51.1 | 21 / 2 | |
| 0.51.0 | 21 / 2 | |
| 0.50.0 | 21 / 2 | |
| 0.49.3 | 21 / 2 | |
| 0.49.2 | 21 / 2 | |
| 0.49.1 | 21 / 2 | |
| 0.49.0 | 21 / 2 | |
| 0.48.14 | 21 / 2 | |
| 0.48.13 | 21 / 2 | |
| 0.48.12 | 21 / 2 | |
| 0.48.11 | 21 / 2 | |
| 0.48.10 | 21 / 2 | |
| 0.48.9 | 21 / 2 | |
| 0.48.8 | 21 / 2 | |
| 0.48.7 | 21 / 2 | |
| 0.48.6 | 21 / 2 | |
| 0.48.5 | 21 / 2 | |
| 0.48.4 | 21 / 2 | |
| 0.48.3 | 21 / 2 | |
| 0.48.2 | 21 / 2 | |
| 0.48.1 | 21 / 2 | |
| 0.48.0 | 21 / 2 | |
| 0.47.4 | 21 / 2 | |
| 0.47.3 | 21 / 2 | |
| 0.47.2 | 21 / 2 | |
| 0.47.1 | 21 / 2 | |
| 0.47.0 | 21 / 2 | |
| 0.46.0 | 21 / 2 | |
| 0.45.0 | 21 / 2 | |
| 0.44.0 | 21 / 2 | |
| 0.43.0 | 21 / 2 | |
| 0.42.7 | 21 / 2 | |
| 0.42.6 | 21 / 2 | |
| 0.42.5 | 21 / 2 | |
| 0.42.4 | 21 / 2 | |
| 0.42.3 | 21 / 2 | |
| 0.42.2 | 21 / 2 | |
| 0.42.1 | 21 / 2 | |
| 0.42.0 | 21 / 2 | |
| 0.41.10 | 21 / 2 | |
| 0.41.9 | 21 / 2 | |
| 0.41.8 | 21 / 2 | |
| 0.41.7 | 21 / 2 | |
| 0.41.6 | 21 / 2 | |
| 0.41.5 | 21 / 2 | |
| 0.41.4 | 21 / 2 | |
| 0.41.3 | 21 / 2 | |
| 0.41.2 | 21 / 2 | |
| 0.41.1 | 21 / 2 | |
| 0.41.0 | 21 / 2 | |
| 0.40.7 | 21 / 2 | |
| 0.40.6 | 21 / 2 | |
| 0.40.5 | 21 / 2 | |
| 0.40.4 | 21 / 2 | |
| 0.40.3 | 21 / 2 | |
| 0.40.2 | 21 / 2 | |
| 0.40.1 | 21 / 2 | |
| 0.40.0 | 21 / 2 | |
| 0.39.3 | 21 / 2 | |
| 0.39.2 | 21 / 2 | |
| 0.39.1 | 21 / 2 | |
| 0.39.0 | 21 / 2 | |
| 0.38.3 | 21 / 2 | |
| 0.38.2 | 21 / 2 | |
| 0.38.1 | 21 / 2 | |
| 0.38.0 | 21 / 2 | |
| 0.37.0 | 21 / 2 | |
| 0.36.5 | 21 / 2 | |
| 0.36.4 | 21 / 2 | |
| 0.36.3 | 21 / 2 | |
| 0.36.2 | 21 / 2 | |
| 0.36.1 | 21 / 2 | |
| 0.36.0 | 21 / 2 | |
| 0.35.6 | 21 / 2 | |
| 0.35.5 | 21 / 2 | |
| 0.35.4 | 21 / 2 | |
| 0.35.3 | 21 / 2 | |
| 0.35.2 | 21 / 2 | |
| 0.35.1 | 21 / 2 |
v0.57.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.42.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.41.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.41.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.41.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.41.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.41.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.41.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.41.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.41.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.41.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.41.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.41.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.40.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.40.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.40.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.40.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.40.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.40.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.40.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.40.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.39.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.39.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.39.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.39.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.38.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.38.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.38.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.38.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.37.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.36.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.36.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.36.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.36.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.36.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.36.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.35.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.35.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.35.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.35.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.35.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.35.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.