1ae5cb8 · 8,388 commits · 1,574 files
Issued 2026-10-22
Nothing significant. Questions worth asking about Security & Reliability Posture, Engineering Process & SDLC Maturity.
104 checks ran across 6 assessable dimensions. 1 finding is worth checking first. 6 findings, each with evidence. One dimension cannot be assessed without an acquirer.
- 04.62 Releases are cut from another branch than the one surveyed
Borehole's proprietary scoring is calibrated across hundreds of repositories. Each finding here reads significant, but its check has not yet held up often enough in that calibration to rate significant on its own. If one holds when someone checks it, it is significant.
- 05.26 69 locked dependencies have published vulnerabilities, 26 high or critical in what ships
- 1 finding from checks Borehole's calibration found wrong more often than right is no longer published.
- 1 finding about one contributor is withheld: one author wrote nearly all of this repository's commits; a buyer of this report reads them.
| Dimension | Rating | ||
|---|---|---|---|
| 01 | Architecture & Codebase — including AI provenance | strong | |
| 02 | Engineering Process & SDLC Maturity | adequate | |
| 03 | Organization & Key-Person Risk | not assessable | |
| 04 | Product & Engineering Maturity | strong | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | adequate | |
| 07 | Fit with the Acquirer | not assessable |
- 26% of non-merge commits carry any trailer at all
- low trailer coverage: the convention may not be in consistent use
- no widespread author/committer date divergence
- deep scan blamed 1,563 of 1,563 counted files
Architecture & Codebase — including AI provenance
01 · strong · ratings ↑packages/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.
A note that does not affect this rating: measured against its own codebase's median, it is below the 85th percentile of 382 surveyed projects' largest files, where this check begins to count.
| line-count | packages/core/src/lib/core/initialise-lists.ts:1 — 1,317 lines (24× median) |
| line-count | packages/core/src/admin-ui/pages/ListPage/index.tsx:1 — 1,052 lines (19× median) |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Engineering Process & SDLC Maturity
02 · adequate · ratings ↑1 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 | tests/cli-tests/artifacts.test.ts:63 — committed .only: other tests do not run |
| packages/fields-document/src/DocumentEditor/insert-menu.test.tsx | packages/fields-document/src/DocumentEditor/insert-menu.test.tsx:219 — skipped test |
| packages/fields-document/src/DocumentEditor/insert-menu.test.tsx | packages/fields-document/src/DocumentEditor/insert-menu.test.tsx:251 — skipped test |
| packages/fields-document/src/DocumentEditor/insert-menu.test.tsx | packages/fields-document/src/DocumentEditor/insert-menu.test.tsx:286 — skipped test |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Organization & Key-Person Risk
03 · not assessable · ratings ↑Not rated: one author wrote nearly all of this repository's commits, so a finding about one contributor would be about someone its history all but names; the public report does not carry those, and does not rate this dimension without them. What a person adds here.
Product & Engineering Maturity
04 · strong · ratings ↑Releases 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.
A note that does not affect this rating: notes like it are common in well-run projects.
| 09685b8e0 | tag v4.0.0 |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Security & Reliability Posture
05 · adequate · ratings ↑69 locked dependencies have published vulnerabilities, 26 high or critical in what ships
adequate worth checking first69 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.
The check that found this reads significant, but it has not yet held up often enough in Borehole's calibration to rate a finding significant on its own. Opening pnpm-lock.yaml settles it. If it holds when someone checks it, this finding is significant.
| pnpm-lock.yaml | pnpm-lock.yaml — next 16.2.10: GHSA-2464-fhr4-w9xw (critical), fixed in 16.4.1 |
| pnpm-lock.yaml | pnpm-lock.yaml — proxy-addr 2.0.7: GHSA-jqcg-44mw-7w3h (critical), fixed in 2.0.8 |
| pnpm-lock.yaml | pnpm-lock.yaml — @remix-run/node 1.19.3: GHSA-9583-h5hc-x8cw (critical), fixed in 2.17.2; a development dependency |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
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, …).
A note that does not affect this rating: it describes the project's advisory record, and no advisory in it is known to affect the surveyed commit.
| GHSA-cqmq-8755-7xvh | 2026-07-01: GHSA-cqmq-8755-7xvh (high), fixed in 6.5.3: Keystone vulnerable to `graphql.maxTake` bypass with negative `take` |
| GHSA-45jq-c8xm-jfw9 | 2026-06-04: GHSA-45jq-c8xm-jfw9 (low): Keystone: GraphQL API Endpoint Lacks Query Depth Limits |
| GHSA-cgcg-q9jh-5pr2 | 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) |
| GHSA-hg9m-67mm-7pg3 | 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 |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Observability & Operations
06 · adequate · ratings ↑Sends 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 | packages/core/src/lib/telemetry.ts:13 — reports to telemetry.keystonejs.com |
| packages/core/src/schema.ts | packages/core/src/schema.ts:181 — the reporting setting is on by default |
Respond to this finding
Your response is published beside the finding, not instead of it. A finding you can argue with is the point — and a wrong one is calibration data we want.
An owner's response is removed only when it is unlawful, impersonates someone, publishes personal data or a credential, or is not about the finding. Disagreeing with the report is never a reason. To report a response, or to reach us about one, write to takedown@borehole.dev.
Fit with the Acquirer
07 · not assessable · ratings ↑Not rated: structurally not assessable from a repository. What a person adds here.
Check it on the running system
3 checks against the running system follow from the findings above: what a buyer's engineer will try, how to run it first, and what to have ready. A paid survey of this repository includes them.
A paid survey of a public repository is also reviewed: a language model reads each finding against the code and withdraws only findings it judges the code contradicts, each listed with its reason. The review is a language model's reading of the findings against the code, and it can be wrong. It never adds a finding, never raises a band, and never removes a finding from a proven check or an advisory that affects the surveyed version.
What a person adds
The survey reads what the repository can show. The code cannot settle these questions, and on them this report states nothing. Each says where its answer lives: your own engineer, the company, or an assessor you choose can settle it. Questions marked measured open with something this repository shows.
Architecture & Codebase — including AI provenance
01 · full coverage- measured The tree carries design documentation (packages/fields-document/ARCHITECTURE.md). Does it match what the team believes today? Ask them to walk through it against the code.
- Is the architecture right for the next three years of the product?
- Were the home-grown components reasonable choices when they were made, and are they now?
Engineering Process & SDLC Maturity
02 · high coverage- Is review real or a rubber stamp? Comment depth and time to approve need the pull request history.
- Is delivery planned and measured, or heroic?
- How are incidents run, reviewed and learned from?
Organization & Key-Person Risk
03 · partial coverageNot rated: one author wrote nearly all of this repository's commits, so a finding about one contributor would be about someone its history all but names; the public report does not carry those, and does not rate this dimension without them.
- Which of the people who wrote this are part of the transaction, and for how long after it?
- Who mentors whom, and would that survive a departure?
- Can the team grow, and who stands behind the top three contributors?
- Is the seniority mix sound, and will pay survive your salary bands?
- Is the pace sustainable? Commit times cannot say: git keeps no reliable local time.
- Does the team want to stay after close?
- How are decisions made and disagreements resolved?
Product & Engineering Maturity
04 · minimal coverage- Can this team deliver the stated roadmap on the stated timeline?
- Does leadership know about the debt, and is time budgeted to repay it?
- Is the engineering shape consistent with the commercial story?
Security & Reliability Posture
05 · partial coverage- What has actually broken, how often, and how badly?
- What did external testing find, and was it fixed?
- What is the SOC 2, ISO 27001 or GDPR status, and where is the evidence?
Observability & Operations
06 · partial coverage- Are the dashboards opened, the alerts acknowledged and the pages answered?
- Are the service-level objectives actually met?
- Who carries the pager, and how often does it go off?
- What does it cost to run, and how much headroom is there?
Fit with the Acquirer
07 · none coverageNot rated: structurally not assessable from a repository.
- This is primarily a TypeScript codebase. Does your engineering organisation already run TypeScript in production, or would this be the first?
- The bulk of this system sits in packages/, tests2/, prisma-utils/. Which of your existing systems would each of those have to absorb or replace?
- Nothing in the repository says how this is deployed. Is it shipped as a library, a binary or a service, and if it runs somewhere, who owns that environment?
- What is your tolerance for the findings above remaining unaddressed for the first two quarters after close, given everything else that will compete for this team's time?
- Which of these systems duplicate yours, and which get retired?
- What will integration cost, and in what order?
- Where does the team land in your organisation, and who reports to whom?
- Are there earn-outs, retention packages or contractor IP to assign?
- Do customer contracts limit hosting, regions or vendors?
A human assessment is Borehole's own paid service, €12,000+ (total price is determined per engagement; travel billed at cost). It is not independent of this report: the same business produced both. It is a separate contract, with its own scope, terms and reliance.
Embed the badge
Tied to this commit and this date, and it fades after 90 days — an honest badge is one that expires. A repository with significant findings gets a neutral "read" badge rather than a red one: the library is where the range is visible, not someone else's README.
[](/r/keystonejs/keystone/1ae5cb8)If you embed it: link it to the report, remove it if the report is delisted, and do not present it as a certification or an endorsement.
Rejection log — 98 signals that ran and did not fire
Appendix: rejection log — 98 signals that ran and did not fire
Published on purpose. A signal that looked and decided not to fire has told you something, and this is the calibration data behind every threshold above.
Looked, and found nothing — 65
| Signal | What it found |
|---|---|
| 04.hotspot_concentration | change is spread across the codebase rather than pooling in a few filesfiles 12,933 · top5 share 0.022 |
| 04.debt_markers | debt markers are sparsemarkers 197 · per kloc 1.43 · lines read 137,434 |
| 04.dependency_sprawl | direct dependency counts are unremarkable |
| 04.test_growth | test effort kept pace with code writtenlate test per code 0.337 · early test per code 0.481 |
| 04.churn_trend | rework is not rising against new worklate delete per insert 0.875 · early delete per insert 0.759 |
| 04.fixes_with_tests | fixes usually come with a testfixes 95 · share 0.232 · with tests 22 |
| 06.telemetry_presence | this repository does not deploy a running service, so instrumentation is not expected of itbasis nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere · files read 1,292 |
| 06.structured_logging | not a running service; structured logging is not expected of a librarybasis nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.healthcheck_presence | not a running service, so a health endpoint is not expectedbasis nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.migrate_on_start | migrations do not run at container start |
| 03.active_contributors | withheld: this check's result would describe one person |
| 03.drive_by_contributors | withheld: this check's result would describe one person |
| 03.contributor_attrition | withheld: this check's result would describe one person |
| 03.critical_path_ownership | withheld: this check's result would describe one person |
| 03.second_contributor_attrition | withheld: this check's result would describe one person |
| 03.bus_factor_trend | withheld: this check's result would describe one person |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 0 · window last 24 months · with tracked 0 |
| 02.ci_presence | CI configuration is present in the working treecount 8 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 231 · source 501 · test ratio 0.461 |
| 02.release_cadence | tags are presenttags 3,484 |
| 02.conventional_commits | commit subjects generally carry contentsampled 7,392 · low content share 0.021 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 8 · with tests 2 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 8 |
| 02.revert_share | change is rarely undoneshare 0.003 · reverts 1 · recent commits 342 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 1 · commits since 3 · days since lockfile changed 36 |
| 02.flaky_test_markers | tests are not retried until they passtest retries 0 · suite retries 0 |
| 02.lint_in_build | a linter or formatter runs in the buildwired 3 · ci configs 8 · product files 270 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.019 · commits 310 · over 2000 lines 6 |
| 01.burst_import | no commit run met both the rate and the net-addition thresholdgap seconds 180 · min add ratio 3.0 · min net added 2,000 |
| 01.initial_dump | first commit is not a disproportionate share of the codebaseinsertions 81 · share of insertions 0.0001 |
| 01.message_uniformity | commit subjects vary in wording and lengthlength stdev 21.75 · repeat share 0.037 |
| 01.revision_depth | most files were revisited after they were first writtenfiles seen 310 · write once share 0.087 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0251 · product files 270 · distinct blocks 28,842 |
| 01.swallowed_errors | errors are rarely thrown awayloc 138,717 · files 3 · per kloc 0.02 |
| 01.unfinished_migration | no language migration is stalled halfway |
| 01.weights_in_git | no model weights are committedfiles 0 |
| 05.committed_secrets | no credential-shaped strings outside test and fixture pathsnote the working tree only; the history is 05.5 · patterns 8 · files read 1,292 |
| 05.security_guardrails | at least one standard guard rail is configured |
| 05.dependency_pinning | a lockfile is committed, so builds are reproduciblelockfile True |
| 05.license_present | a licence file is presentfound True |
| 05.secrets_in_history | no credential-shaped string was ever added outside test and fixture pathspatterns 8 · truncated False · added lines 1,273,410 |
| 05.secrets_management_pattern | no environment file is committed outside tests and examplesenv files 0 |
| 05.supply_chain_pinning | third-party build steps are pinned, or fewaction refs 29 · pipe to shell 0 · unpinned third party 2 |
| 05.shell_from_strings | product code does not build shell commands from stringssites 0 |
| 05.unsafe_deserialization | no code-executing deserialiser in product codesites 0 |
| 05.tls_verification_off | no TLS verification is switched off in product codefiles 0 · sites 0 · pinned instead 0 |
| 05.privileged_workloads | no workload runs privileged or in the host's namespacessites 0 · behind a setting or built here 0 |
| 05.credentials_in_deploy_config | deployment configuration references secrets, never holds themfiles 0 · sites 0 |
| 05.public_env_secret | only publishable values carry a public prefixnames 0 · sites 0 · not secrets 0 |
| 05.unsafe_html | raw HTML is rare, literal or sanitisedsites 0 |
| 05.source_maps_shipped | production builds do not publish source mapssites 0 |
| 05.signing_material | no signing keystore or profile is committedfiles 0 |
| 05.license_manifest_conflict | manifest and licence file agree on MITlicense MIT |
| 05.license_vendored_unlicensed | no vendored third-party code is committedcomponents 0 |
| 05.license_grant_unclear | the licence is recognisable as MITclass permissive · license MIT |
| 05.committed_native_libraries | no widely used compiled library is committed to the productlibraries 0 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 307 · added in two years 25 · removed within 60 days 1 |
| 04.ci_platforms_dropped | no platform was dropped from CI in the last two years |
| 04.repository_status | the README's first screen states no end, move or freezestatements 0 |
| 02.development_elsewhere | nothing says development happens elsewhereno pr statements 0 · mirror statements 0 · replayed commit share 0.0 |
| 05.licence_changes | the root licence has not changed in the history readlicence versions 1 · unreleased changes 0 |
| 05.paid_edition | no directory carries a separate paid-edition licencedirectories 0 |
| 04.releases_stopped | releases keep pace with developmentmedian gap days 0.0 · days since last tag 52 · commits last 90 days 82 |
| 03.single_maintainer | withheld: this check's result would describe one person |
Could not conclude, or did not apply — 33
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.eol_runtime | no pinned runtime version to check |
| 04.fix_share_trend | fewer than six busy quarters to compare |
| 04.schema_churn | no schema migrations to read |
| 04.compat_layers | a library, whose compatibility code is usually deliberate |
| 04.dependency_redundancy | no JavaScript manifest to read |
| 06.telemetry_depth | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.print_logging | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.correlation_ids | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.error_reporting | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.alert_rules | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.deployed_image_floats | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.probes_identical | no Kubernetes probes |
| 06.single_replica | no Kubernetes deployments |
| 06.environment_branching | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.release_markers | not expected of it: nothing in this repository deploys a long-running server; if it runs as one, its deployment lives elsewhere |
| 06.feature_flags | no feature-flag service; flags may live elsewhere |
| 03.joiners_and_leavers | withheld: this check's result would describe one person |
| 02.long_lived_branches | too few merges to judge (squash and rebase leave none) |
| 01.build_reproducibility | no product Dockerfile to read |
| 01.notebook_outputs | not a data or machine-learning repository |
| 05.container_runs_as_root | no Dockerfile to read |
| 05.outbound_timeouts | not a running service |
| 05.migration_reversibility | too few migrations to judge |
| 05.sql_from_strings | not a running service; a library that builds SQL is doing its job |
| 05.resource_limits | no Kubernetes workload manifests |
| 05.cleartext_traffic | not a mobile app |
| 05.dataset_provenance | not a data or machine-learning repository |
| 05.license_copyleft_inherited | no third-party code is committed to this repository, so the licences it depends on are resolved at build time and are not readable here |
| 04.flags_accumulating | few or no feature flags in the history |
| 04.api_versions_coexisting | not a running service |
| 04.deprecations_lingering | a library, which keeps deprecated interfaces for its users |
| 05.project_advisories | record incomplete: no advisory found in the sources that answered; OSV npm @keystone-6/cloudinary (an empty record for a package published here), OSV npm create-keystone-app (an empty record for a package published here), OSV npm @keystone-6/document-renderer (an empty record for a package published here), OSV npm @keystone-6/fields-document (an empty record for a package published here) did not; NVD: 45 records name keystone with nothing tying them to this repository (CVE-2006-1578, CVE-2012-1572, CVE-2012-3426, …) |
| 05.project_exploited | no affecting advisory is on CISA's Known Exploited list |
Anyone can check this report against the authoritative record — click the stamp, or enter V988-9PS0-6ANC at borehole.dev/verify.
The code commits to the 106 checks this run performed, the bands they produced, and the commit they were read at. It does not cover checks written since.
Put the mark in your README
The image is wrapped in a link to the verification page, so a reader can check it rather than take it on trust. If you embed it: link it to the report, remove it if the report is delisted, and do not present it as a certification or an endorsement.
[](https://borehole.dev/verify/V9889PS06ANC?via=badge)
Where this scan ran
This scan ran on ordinary cloud infrastructure (cloud-run), not in a hardware-isolated confidential VM. Nothing about it is attested by Google.
What an attested survey proves, and what it does not.
What this scan did with the repository — 7 steps
Written by the steps themselves as they ran, not described afterwards. A hand-written account of a data flow drifts the first time somebody changes the flow and not the account.
| At | Step | Detail |
|---|---|---|
| 0.0s | read repository metadata from the GitHub API | size mb: 375.3authenticated: False |
| 31.6s | cloned the repository to a temporary directory | depth: full |
| 55.5s | read the git history | commits: 8388tracked files: 1574 |
| 238.7s | ran the deterministic checks | blame pass: Trueread working tree: False |
| 238.7s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 290.6s | kept the facts, never the source, for re-reading under new checks | |
| 290.6s | deleting the working copy |
Total 290.6s ·source content sent off this machine: none · calls to a language model: 0 · the clone was deleted when the survey ended
An automated reading of a repository's code and its history up to one commit, with public advisory records. It may be wrong, it is not legal, financial, investment or security advice, and it does not replace diligence by a qualified person. It is provided for information: nobody may rely on it (Borehole's terms, section 3).