payload
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate handoff among payloadcms org maintainers; no material changes. | ai | |
| phantom-deps | phantom-dep:@types/busboy | AI (phantom-deps): @types/busboy is an explicit dependency in package.json; used for type resolution, not direct import. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 3.86.0 | 31 / 18 | |
| 3.85.2 | 31 / 18 | |
| 3.85.1 | 31 / 18 | |
| 3.85.0 | 31 / 18 | |
| 3.84.1 | 31 / 18 | |
| 3.84.0 | 31 / 18 | |
| 3.83.0 | 31 / 18 | |
| 3.82.1 | 31 / 19 | |
| 3.82.0 | 31 / 19 | |
| 3.81.0 | 31 / 19 | |
| 3.80.0 | 31 / 19 | |
| 3.79.1 | 31 / 19 |
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.81.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-01. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.80.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.79.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.