@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 9 of 209)
| Version | Deps | Published |
|---|---|---|
| 0.11.0 | 13 / 1 | |
| 0.10.4 | 13 / 1 | |
| 0.10.3 | 13 / 1 | |
| 0.10.2 | 13 / 1 | |
| 0.10.1 | 13 / 1 | |
| 0.10.0 | 13 / 1 | |
| 0.9.2 | 13 / 1 | |
| 0.9.1 | 13 / 1 | |
| 0.9.0 | 13 / 1 |
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.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.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.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.