@lion/ui
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped package @lion/ui; Levenshtein match to uuid is a false positive. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @lion/ui; Levenshtein match to pg is a false positive. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @lion/ui; Levenshtein match to qs is a false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @lion/ui; Levenshtein match to joi is a false positive. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped package @lion/ui; Levenshtein match to yup is a false positive. | ai | |
| dependencies | unvetted-dep:ibantools | AI (dependencies): ibantools is a legitimate IBAN validation library used by this design system's input-iban component. | ai | |
| dependencies | unvetted-dep:singleton-manager | AI (dependencies): singleton-manager is a sibling package in the ing-bank/lion monorepo. | ai | |
| dependencies | unvetted-dep:@bundled-es-modules/message-format | AI (dependencies): Known ES module wrapper for message-format; legitimate dependency for localization. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.20.0 | 9 / 0 | |
| 0.19.1 | 9 / 0 | |
| 0.18.1 | 9 / 0 | |
| 0.18.0 | 9 / 0 | |
| 0.17.1 | 9 / 0 | |
| 0.17.0 | 9 / 0 | |
| 0.16.1 | 9 / 0 | |
| 0.16.0 | 9 / 0 | |
| 0.15.5 | 9 / 0 | |
| 0.15.4 | 9 / 0 | |
| 0.15.3 | 9 / 0 |
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.