@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, 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: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 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 3.86.0 | 23 / 13 | |
| 3.85.2 | 23 / 13 | |
| 3.85.1 | 23 / 13 | |
| 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 | |
| 3.80.0 | 23 / 14 | |
| 3.79.1 | 23 / 14 | |
| 3.79.0 | 23 / 14 | |
| 3.78.0 | 23 / 14 | |
| 3.77.0 | 23 / 14 | |
| 3.76.1 | 23 / 14 | |
| 3.76.0 | 23 / 14 | |
| 3.75.0 | 23 / 14 | |
| 3.74.0 | 23 / 14 | |
| 3.73.0 | 23 / 14 | |
| 3.72.0 | 23 / 14 | |
| 3.71.1 | 23 / 14 | |
| 3.71.0 | 23 / 14 | |
| 3.70.0 | 23 / 14 | |
| 3.69.0 | 23 / 14 | |
| 3.68.5 | 23 / 14 | |
| 3.68.4 | 23 / 14 | |
| 3.68.3 | 23 / 14 | |
| 3.68.2 | 23 / 14 | |
| 3.68.1 | 23 / 14 | |
| 3.68.0 | 23 / 14 | |
| 3.67.0 | 23 / 14 | |
| 3.66.0 | 23 / 14 | |
| 3.65.0 | 23 / 14 | |
| 3.64.0 | 23 / 14 | |
| 3.63.0 | 23 / 14 | |
| 3.62.1 | 23 / 14 | |
| 3.62.0 | 23 / 14 |
v3.86.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.85.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.80.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.79.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.79.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.78.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.77.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.76.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.76.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.75.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.74.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.73.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.72.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.71.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.71.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.70.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.69.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.68.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.68.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.68.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.68.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.68.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.68.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.67.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.66.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.65.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.64.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.63.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.62.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.62.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.