@tonconnect/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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Established publisher with clean history; missing gitHead alone is insufficient to block a minor patch release with no other risk signals. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped package @tonconnect/ui; Levenshtein match to uuid is a false positive. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped package @tonconnect/ui; Levenshtein match to pg is a false positive. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped package @tonconnect/ui; Levenshtein match to qs is a false positive. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped package @tonconnect/ui; Levenshtein match to joi is a false positive. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped package @tonconnect/ui; Levenshtein match to yup is a false positive. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 2.4.4 | 5 / 19 | |
| 2.4.3 | 5 / 19 | |
| 2.4.2 | 5 / 19 | |
| 2.4.1 | 5 / 19 | |
| 2.4.0 | 5 / 19 | |
| 2.3.1 | 5 / 17 | |
| 2.3.0 | 5 / 17 | |
| 2.2.0 | 5 / 18 |
v2.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: thekiba.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.