@payloadcms/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
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 @payloadcms/ui; Levenshtein match to short names is a false positive for this established CMS package. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Same false-positive pattern; scoped namespace clearly not impersonating pg. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Same false-positive pattern; scoped namespace clearly not impersonating qs. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Same false-positive pattern; scoped namespace clearly not impersonating joi. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Same false-positive pattern; scoped namespace clearly not impersonating yup. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 3.85.0 | 23 / 13 | |
| 3.84.1 | 23 / 13 | |
| 3.84.0 | 23 / 13 | |
| 3.83.0 | 23 / 13 | |
| 3.82.1 | 23 / 14 | |
| 3.82.0 | 23 / 14 | |
| 3.81.0 | 23 / 14 |
v3.85.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.84.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.83.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.82.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.82.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.81.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.