Read 2026-10-04
payloadcms/payload: technical due diligence, read from its repository
What Borehole read in payloadcms/payload's code and history at 124b55a: its licence, security advisories, releases, review practice, tests, dependencies and operations. Every finding cites the file and line it rests on. The full report also covers the team and asks the questions the code cannot answer.
| Dimension | Rating |
|---|---|
| Architecture & Codebase — including AI provenance | strong |
| Engineering Process & SDLC Maturity | strong |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
CONTRIBUTING.md:43: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongtemplates/with-cloudflare-d1/cloudflare-env.d.ts is 12,012 lines, 273× this codebase's median file
adequateThe median source file here is 44 lines. 19 files exceed 1,000 lines, the largest being 12,012. Size is not a defect on its own — some problems genuinely live in one place — but these are where merge conflicts, review fatigue and single-owner knowledge concentrate, and they are the first thing that slows an inheriting engineer down.
templates/with-cloudflare-d1/cloudflare-env.d.ts:1 — 12,012 lines (273× median) |
packages/payload/src/fields/config/types.ts:1 — 2,145 lines (48× median) |
packages/payload/src/index.ts:1 — 2,123 lines (48× median) |
packages/payload/src/config/types.ts:1 — 2,052 lines (46× median) |
templates/ecommerce/src/payload-types.ts:1 — 1,904 lines (43× median) |
Engineering Process & SDLC Maturity
strongTests are retried until they pass
adequateThe suite is configured to retry failing tests (templates/_template/playwright.config.ts). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.
templates/_template/playwright.config.ts:17 — test retry |
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, v3.90.2, is not on the branch this survey read; the newest release on it is v3.84.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v3.90.2 |
Security & Reliability Posture
adequate14 SQL statements built from strings
adequate14 places in product code build SQL by formatting or joining strings rather than passing parameters. 4 of them put a value into the string; in the rest, what the code shows going in is a table or column name, a constant, or something the line does not show. Ask whether any value reaches these strings, rather than a parameter.
packages/db-sqlite/src/predefinedMigrations/migrateLocalizeStatus.ts:79 — SQL built from a string |
packages/drizzle/src/sqlite/predefinedMigrations/localize-status/index.ts:221 — SQL built from a string |
packages/drizzle/src/sqlite/predefinedMigrations/localize-status/index.ts:243 — SQL built from a string |
43 locked dependencies have published vulnerabilities, 33 high or critical in what ships
adequate43 of 2,715 locked dependencies match 146 published advisories in OSV, 61 of them rated high or critical. A lockfile says which version is installed, not whether the flawed code is reachable from this product, so each needs a look. Most are fixed by an upgrade, and the advisory names the version.
pnpm-lock.yaml — next 16.3.3: GHSA-vcvr-r3jv-pc5j (critical), fixed in 16.3.6 |
pnpm-lock.yaml — @xhmikosr/decompress 10.2.1: GHSA-hrh2-vp3x-79xf (critical), fixed in 10.2.2; a development dependency |
pnpm-lock.yaml — fast-xml-parser 4.2.5: GHSA-m7jm-9gc2-mpf2 (critical), fixed in 4.5.4; a development dependency |
10 places insert HTML from a variable without sanitising it
adequate10 places set HTML from a value that is neither a literal nor passed through a sanitiser. Where the value can come from a user, that is stored cross-site scripting, and it is the first thing a buyer's security review looks for in a frontend.
packages/richtext-lexical/src/features/converters/lexicalToJSX/converter/index.tsx:40 — HTML from a variable |
packages/richtext-lexical/src/features/converters/lexicalToJSX/converter/index.tsx:88 — HTML from a variable |
packages/richtext-lexical/src/field/Diff/converters/listitem/index.tsx:35 — HTML from a variable |
39 advisories against this project in the last 24 months, 27 high or critical
adequateThe newest was published on 2026-09-29. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 30 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 3.84.0. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: its keyword search for 'payload' is too broad to read whole (6,315 records).
| 2026-09-29: GHSA-q6mq-ch85-c8mm (moderate), fixed in >= 3.90.0: Password hashes use insufficient PBKDF2 iterations |
| 2026-09-25: GHSA-mc8m-rr6c-r5qr (moderate), fixed in >= 3.90.0: Access control bypass of uploads in Vercel Storage adapter |
| 2026-09-22: GHSA-w84c-53h3-mc2g (moderate), fixed in >= 3.88.0: Untrusted redirect URL parameter exploit |
| 2026-09-22: GHSA-9g87-32v6-3c2r (moderate), fixed in >= 3.88.0: Sort queries could expose protected field information |
| 2026-09-22: GHSA-2q76-m6w6-qgc6 (high), fixed in >= 3.88.0: Improper access control for MCP API keys |
Observability & Operations
adequateSends usage data to telemetry.payloadcms.com by default
adequatepackages/payload/src/utilities/telemetry/index.ts sends to telemetry.payloadcms.com, and packages/payload/src/config/defaults.ts leaves reporting on as shipped. Every installation reports to the vendor unless its operator turns this off. For a buyer running it inside their own product, that is an outbound data flow to a third party: ask what is sent, how often, and whether the buyer's customers were told.
packages/payload/src/utilities/telemetry/index.ts:101 — reports to telemetry.payloadcms.com |
packages/payload/src/config/defaults.ts:137 — the reporting setting is on by default |
2 of 5 deployed images carry no version, or `latest`
adequate2 images in the deployment configuration are named without a version or as `latest`. A redeploy can change the software without a commit, a rollback has nothing to roll back to, and nobody can say from the repository what is running.
templates/with-vercel-mongodb/docker-compose.yml:21 — image without a version |
templates/with-vercel-postgres/docker-compose.yml:22 — image without a version |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on payloadcms/payload: every dimension, the questions for the room, and the audit log.
Survey a repository: free on public repositories. Private code is read on your own machine by a collector whose source you can read first.