@dile/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 @dile/ui; Levenshtein match to uuid is a false positive. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @dile/ui; Levenshtein match to pg is a false positive. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @dile/ui; Levenshtein match to qs is a false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @dile/ui; Levenshtein match to joi is a false positive. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped package @dile/ui; Levenshtein match to yup is a false positive. | ai |
Versions (showing 100 of 137)
| Version | Deps | Published |
|---|---|---|
| 3.0.2 | 2 / 0 | |
| 3.0.1 | 2 / 0 | |
| 3.0.0 | 2 / 0 | |
| 2.28.0 | 2 / 0 | |
| 2.27.4 | 2 / 0 | |
| 2.27.3 | 2 / 0 | |
| 2.27.2 | 2 / 0 | |
| 2.27.1 | 2 / 0 | |
| 2.27.0 | 2 / 0 | |
| 2.26.0 | 2 / 0 | |
| 2.25.7 | 2 / 0 | |
| 2.25.6 | 2 / 0 | |
| 2.25.4 | 2 / 0 | |
| 2.25.3 | 2 / 0 | |
| 2.25.2 | 2 / 0 | |
| 2.25.1 | 2 / 0 | |
| 2.25.0 | 2 / 0 | |
| 2.24.2 | 2 / 0 | |
| 2.24.1 | 2 / 0 | |
| 2.24.0 | 2 / 0 | |
| 2.23.12 | 2 / 0 | |
| 2.23.11 | 2 / 0 | |
| 2.23.10 | 2 / 0 | |
| 2.23.9 | 2 / 0 | |
| 2.23.8 | 2 / 0 | |
| 2.23.7 | 2 / 0 | |
| 2.23.6 | 2 / 0 | |
| 2.23.5 | 2 / 0 | |
| 2.23.4 | 2 / 0 | |
| 2.23.3 | 2 / 0 | |
| 2.23.1 | 2 / 0 | |
| 2.23.0 | 2 / 0 | |
| 2.22.1 | 2 / 0 | |
| 2.22.0 | 2 / 0 | |
| 2.21.4 | 2 / 0 | |
| 2.21.3 | 2 / 0 | |
| 2.21.2 | 2 / 0 | |
| 2.21.1 | 2 / 0 | |
| 2.21.0 | 2 / 0 | |
| 2.20.1 | 2 / 0 | |
| 2.20.0 | 2 / 0 | |
| 2.19.0 | 2 / 0 | |
| 2.18.3 | 2 / 0 | |
| 2.18.2 | 2 / 0 | |
| 2.18.1 | 2 / 0 | |
| 2.18.0 | 2 / 0 | |
| 2.17.1 | 2 / 0 | |
| 2.17.0 | 2 / 0 | |
| 2.16.2 | 2 / 0 | |
| 2.16.1 | 2 / 0 | |
| 2.16.0 | 2 / 0 | |
| 2.15.1 | 2 / 0 | |
| 2.15.0 | 2 / 0 | |
| 2.14.3 | 2 / 0 | |
| 2.14.2 | 2 / 0 | |
| 2.14.1 | 2 / 0 | |
| 2.14.0 | 2 / 0 | |
| 2.13.1 | 2 / 0 | |
| 2.13.0 | 2 / 0 | |
| 2.12.1 | 2 / 0 | |
| 2.12.0 | 2 / 0 | |
| 2.11.1 | 2 / 0 | |
| 2.11.0 | 2 / 0 | |
| 2.10.5 | 2 / 0 | |
| 2.10.4 | 2 / 0 | |
| 2.10.3 | 2 / 0 | |
| 2.10.2 | 2 / 0 | |
| 2.10.1 | 2 / 0 | |
| 2.9.0 | 2 / 0 | |
| 2.8.8 | 2 / 0 | |
| 2.8.6 | 2 / 0 | |
| 2.8.5 | 2 / 0 | |
| 2.8.4 | 2 / 0 | |
| 2.8.3 | 2 / 0 | |
| 2.8.1 | 2 / 0 | |
| 2.8.0 | 2 / 0 | |
| 2.7.1 | 2 / 0 | |
| 2.7.0 | 2 / 0 | |
| 2.6.2 | 2 / 0 | |
| 2.6.1 | 2 / 0 | |
| 2.6.0 | 2 / 0 | |
| 2.5.6 | 2 / 0 | |
| 2.5.5 | 2 / 0 | |
| 2.5.4 | 2 / 0 | |
| 2.5.3 | 2 / 0 | |
| 2.5.2 | 2 / 0 | |
| 2.5.1 | 2 / 0 | |
| 2.5.0 | 2 / 0 | |
| 2.4.3 | 2 / 0 | |
| 2.4.2 | 2 / 0 | |
| 2.4.1 | 2 / 0 | |
| 2.4.0 | 2 / 0 | |
| 2.3.1 | 2 / 0 | |
| 2.3.0 | 2 / 0 | |
| 2.2.0 | 2 / 0 | |
| 2.1.39 | 2 / 0 | |
| 2.1.38 | 2 / 0 | |
| 2.1.37 | 2 / 0 | |
| 2.1.36 | 2 / 0 | |
| 2.1.35 | 2 / 0 |
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.