@snack-uikit/link
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:pino | AI (typosquat): Scoped UI kit package; Levenshtein match to 'pino' is coincidental and not a typosquat. | ai |
Versions (showing 76 of 76)
| Version | Deps | Published |
|---|---|---|
| 0.18.3 | 3 / 0 | |
| 0.18.2 | 3 / 0 | |
| 0.18.1 | 3 / 0 | |
| 0.18.0 | 3 / 0 | |
| 0.17.20 | 3 / 0 | |
| 0.17.19 | 3 / 0 | |
| 0.17.18 | 3 / 0 | |
| 0.17.17 | 3 / 0 | |
| 0.17.16 | 3 / 0 | |
| 0.17.15 | 3 / 0 | |
| 0.17.14 | 3 / 0 | |
| 0.17.13 | 3 / 0 | |
| 0.17.12 | 3 / 0 | |
| 0.17.11 | 3 / 0 | |
| 0.17.10 | 3 / 0 | |
| 0.17.9 | 3 / 0 | |
| 0.17.8 | 3 / 0 | |
| 0.17.7 | 3 / 0 | |
| 0.17.6 | 3 / 0 | |
| 0.17.5 | 3 / 0 | |
| 0.17.4 | 3 / 0 | |
| 0.17.3 | 3 / 0 | |
| 0.17.2 | 3 / 0 | |
| 0.17.1 | 3 / 0 | |
| 0.17.0 | 3 / 0 | |
| 0.16.5 | 3 / 0 | |
| 0.16.4 | 3 / 0 | |
| 0.16.3 | 3 / 0 | |
| 0.16.2 | 3 / 0 | |
| 0.16.1 | 3 / 0 | |
| 0.16.0 | 3 / 0 | |
| 0.15.13 | 3 / 0 | |
| 0.15.12 | 3 / 0 | |
| 0.15.11 | 3 / 0 | |
| 0.15.10 | 3 / 0 | |
| 0.15.9 | 3 / 0 | |
| 0.15.8 | 3 / 0 | |
| 0.15.7 | 3 / 0 | |
| 0.15.6 | 3 / 0 | |
| 0.15.5 | 3 / 0 | |
| 0.15.4 | 3 / 0 | |
| 0.15.3 | 3 / 0 | |
| 0.15.2 | 3 / 0 | |
| 0.15.1 | 3 / 0 | |
| 0.15.0 | 3 / 0 | |
| 0.14.0 | 3 / 0 | |
| 0.13.4 | 3 / 0 | |
| 0.13.3 | 3 / 0 | |
| 0.13.2 | 3 / 0 | |
| 0.13.1 | 3 / 0 | |
| 0.13.0 | 3 / 0 | |
| 0.12.4 | 4 / 0 | |
| 0.12.3 | 4 / 0 | |
| 0.12.2 | 4 / 0 | |
| 0.12.1 | 4 / 0 | |
| 0.12.0 | 4 / 0 | |
| 0.11.10 | 4 / 0 | |
| 0.11.9 | 4 / 0 | |
| 0.11.8 | 4 / 0 | |
| 0.11.7 | 4 / 0 | |
| 0.11.6 | 4 / 0 | |
| 0.11.5 | 4 / 0 | |
| 0.11.4 | 4 / 0 | |
| 0.11.3 | 4 / 0 | |
| 0.11.2 | 4 / 0 | |
| 0.11.1 | 4 / 0 | |
| 0.11.0 | 4 / 0 | |
| 0.10.2 | 4 / 0 | |
| 0.10.1 | 4 / 0 | |
| 0.10.0 | 4 / 0 | |
| 0.9.3 | 4 / 0 | |
| 0.9.2 | 4 / 0 | |
| 0.9.1 | 4 / 0 | |
| 0.9.0 | 4 / 0 | |
| 0.8.1 | 4 / 0 | |
| 0.8.0 | 4 / 0 |
v0.18.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.