Read 2026-10-22
keystonejs/keystone: technical due diligence, read from its repository
What Borehole read in keystonejs/keystone's code and history at 1ae5cb8: 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 | adequate |
| 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
Architecture & Codebase — including AI provenance
strongpackages/core/src/lib/core/initialise-lists.ts is 1,317 lines, 24× this codebase's median file
adequateThe median source file here is 54 lines. 2 files exceed 1,000 lines, the largest being 1,317. 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.
packages/core/src/lib/core/initialise-lists.ts:1 — 1,317 lines (24× median) |
packages/core/src/admin-ui/pages/ListPage/index.tsx:1 — 1,052 lines (19× median) |
Engineering Process & SDLC Maturity
adequate1 committed .only switches other tests off
adequate1 test file commits a focused `.only`, which runs that test and silently skips the rest of its suite. 7 skip markers across 2 of 277 test files. Each is a failure somebody chose to stop seeing; the question is whether anyone is tracking them.
tests/cli-tests/artifacts.test.ts:63 — committed .only: other tests do not run |
packages/fields-document/src/DocumentEditor/insert-menu.test.tsx:219 — skipped test |
packages/fields-document/src/DocumentEditor/insert-menu.test.tsx:251 — skipped test |
packages/fields-document/src/DocumentEditor/insert-menu.test.tsx:286 — skipped test |
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, v4.0.0, is not on the branch this survey read. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v4.0.0 |
Security & Reliability Posture
adequate69 locked dependencies have published vulnerabilities, 26 high or critical in what ships
adequate69 of 2,215 locked dependencies match 150 published advisories in OSV, 85 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.2.10: GHSA-2464-fhr4-w9xw (critical), fixed in 16.4.1 |
pnpm-lock.yaml — proxy-addr 2.0.7: GHSA-jqcg-44mw-7w3h (critical), fixed in 2.0.8 |
pnpm-lock.yaml — @remix-run/node 1.19.3: GHSA-9583-h5hc-x8cw (critical), fixed in 2.17.2; a development dependency |
4 advisories against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-07-01. 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 4 of them are fixed in the code you ship could not be told from this history. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 45 records name keystone with nothing tying them to this repository (CVE-2006-1578, CVE-2012-1572, CVE-2012-3426, …).
| 2026-07-01: GHSA-cqmq-8755-7xvh (high), fixed in 6.5.3: Keystone vulnerable to `graphql.maxTake` bypass with negative `take` |
| 2026-06-04: GHSA-45jq-c8xm-jfw9 (low): Keystone: GraphQL API Endpoint Lacks Query Depth Limits |
| 2026-03-19: GHSA-cgcg-q9jh-5pr2 (moderate), fixed in 6.5.2: @keystone-6/core: `isFilterable` bypass via `cursor` parameter in findMany (CVE-2025-46720 incomplete fix) |
| 2025-05-05: GHSA-hg9m-67mm-7pg3 (low), fixed in 6.5.0: Keystone has an unintended `isFilterable` bypass that can be used as an oracle to match hidden fields |
Observability & Operations
adequateSends usage data to telemetry.keystonejs.com by default
adequatepackages/core/src/lib/telemetry.ts sends to telemetry.keystonejs.com, and packages/core/src/schema.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/core/src/lib/telemetry.ts:13 — reports to telemetry.keystonejs.com |
packages/core/src/schema.ts:181 — the reporting setting is on by default |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on keystonejs/keystone: 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.