@snack-uikit/info-block
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/utils | AI (dependencies): Same-monorepo sibling package; stable false positive for this UI kit. | ai | |
| dependencies | unvetted-dep:@snack-uikit/button | AI (dependencies): Same-monorepo sibling package; stable false positive for this UI kit. | ai | |
| dependencies | unvetted-dep:@snack-uikit/tooltip | AI (dependencies): Same-monorepo sibling package; stable false positive for this UI kit. | ai | |
| dependencies | unvetted-dep:@snack-uikit/typography | AI (dependencies): Same-monorepo sibling package; stable false positive for this UI kit. | ai | |
| dependencies | unvetted-dep:@snack-uikit/icon-predefined | AI (dependencies): Same-monorepo sibling package; stable false positive for this UI kit. | ai |
Versions (showing 67 of 67)
| Version | Deps | Published |
|---|---|---|
| 0.6.43 | 6 / 0 | |
| 0.6.42 | 6 / 0 | |
| 0.6.41 | 6 / 0 | |
| 0.6.40 | 6 / 0 | |
| 0.6.39 | 6 / 0 | |
| 0.6.38 | 6 / 0 | |
| 0.6.37 | 6 / 0 | |
| 0.6.36 | 6 / 0 | |
| 0.6.35 | 6 / 0 | |
| 0.6.34 | 6 / 0 | |
| 0.6.33 | 6 / 0 | |
| 0.6.32 | 6 / 0 | |
| 0.6.31 | 6 / 0 | |
| 0.6.30 | 6 / 0 | |
| 0.6.29 | 6 / 0 | |
| 0.6.28 | 6 / 0 | |
| 0.6.27 | 6 / 0 | |
| 0.6.26 | 6 / 0 | |
| 0.6.25 | 6 / 0 | |
| 0.6.24 | 6 / 0 | |
| 0.6.23 | 6 / 0 | |
| 0.6.22 | 6 / 0 | |
| 0.6.21 | 6 / 0 | |
| 0.6.20 | 6 / 0 | |
| 0.6.19 | 6 / 0 | |
| 0.6.18 | 6 / 0 | |
| 0.6.17 | 6 / 0 | |
| 0.6.16 | 6 / 0 | |
| 0.6.15 | 6 / 0 | |
| 0.6.14 | 6 / 0 | |
| 0.6.13 | 6 / 0 | |
| 0.6.12 | 6 / 0 | |
| 0.6.11 | 6 / 0 | |
| 0.6.10 | 6 / 0 | |
| 0.6.9 | 6 / 0 | |
| 0.6.8 | 6 / 0 | |
| 0.6.7 | 6 / 0 | |
| 0.6.6 | 6 / 0 | |
| 0.6.5 | 6 / 0 | |
| 0.6.4 | 6 / 0 | |
| 0.6.3 | 6 / 0 | |
| 0.6.2 | 6 / 0 | |
| 0.6.1 | 6 / 0 | |
| 0.6.0 | 6 / 0 | |
| 0.5.0 | 6 / 0 | |
| 0.4.9 | 6 / 0 | |
| 0.4.8 | 6 / 0 | |
| 0.4.7 | 6 / 0 | |
| 0.4.6 | 6 / 0 | |
| 0.4.5 | 6 / 0 | |
| 0.4.4 | 6 / 0 | |
| 0.4.3 | 6 / 0 | |
| 0.4.2 | 6 / 0 | |
| 0.4.1 | 6 / 0 | |
| 0.4.0 | 6 / 0 | |
| 0.3.6 | 6 / 0 | |
| 0.3.5 | 6 / 0 | |
| 0.3.4 | 6 / 0 | |
| 0.3.3 | 6 / 0 | |
| 0.3.2 | 6 / 0 | |
| 0.3.1 | 6 / 0 | |
| 0.3.0 | 6 / 0 | |
| 0.2.0 | 6 / 0 | |
| 0.1.3 | 5 / 0 | |
| 0.1.2 | 5 / 0 | |
| 0.1.1 | 5 / 0 | |
| 0.1.0 | 5 / 0 |
v0.6.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.