@payloadcms/next
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:nuxt | AI (typosquat): Legitimate @payloadcms scoped package for Next.js integration; not a typosquat of nuxt. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Legitimate @payloadcms scoped package; Levenshtein match to jest is coincidental. | ai | |
| typosquat | typosquat.levenshtein:knex | AI (typosquat): Legitimate @payloadcms scoped package; Levenshtein match to knex is coincidental. | ai | |
| phantom-deps | phantom-dep:sass | AI (phantom-deps): sass is used via esbuild-sass-plugin at build time; indirect usage pattern is stable for this package. | ai | |
| phantom-deps | phantom-dep:busboy | AI (phantom-deps): busboy used for multipart form handling in Next.js routes; indirect import pattern is stable. | ai | |
| phantom-deps | phantom-dep:file-type | AI (phantom-deps): file-type used for file upload validation; indirect import pattern is stable for this package. | ai |
v3.85.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.84.1
2 findingsPackage name '@payloadcms/next' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.80.0
2 findingsPackage name '@payloadcms/next' is 1 edit(s) away from popular package 'nuxt'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.