d30c905 · 50,000 commits · 20,517 files
Issued 2026-10-22
BUSL-1.1 since 2019-06-04: source available, not open source; production use restricted until the change date.
104 checks ran across 6 assessable dimensions. 4 findings are worth checking first. 16 findings, each with evidence. One dimension cannot be assessed without an acquirer.
- 05.60 BUSL-1.1 since 2019-06-04: source available, not open source; production use restricted until the change date
- 04.62 Releases are cut from another branch than the one surveyed
- 05.60 Relicensed: Apache-2.0 → BUSL-1.1 (2019-06-04) LICENSE
- 4 submodule(s) this survey does not read: c-deps/jemalloc, c-deps/krb5, c-deps/geos .gitmodules:1
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.
- 2 findings from checks Borehole's calibration found wrong more often than right are no longer published.
| Dimension | Rating | ||
|---|---|---|---|
| 01 | Architecture & Codebase — including AI provenance | strong | |
| 02 | Engineering Process & SDLC Maturity | strong | |
| 03 | Organization & Key-Person Risk | strong | |
| 04 | Product & Engineering Maturity | adequate | |
| 05 | Security & Reliability Posture | adequate | |
| 06 | Observability & Operations | adequate | |
| 07 | Fit with the Acquirer | not assessable |
- 7% of non-merge commits carry any trailer at all
- low trailer coverage: the convention may not be in consistent use
- 44% of commits show author/committer date divergence, which is the shape of replayed history that can drop trailers
Architecture & Codebase — including AI provenance
01 · strong · ratings ↑pkg/sql/colexec/colexecprojconst/proj_const_left_ops.eg.go is 26,463 lines, 183× this codebase's median file
adequateThe median source file here is 144 lines. 223 files exceed 1,440 lines, the largest being 26,463. 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. Measured against its own codebase's median, it is larger than 89% of 382 surveyed projects' largest files.
A note that does not affect this rating: notes like it are common in well-run projects.
| line-count | pkg/sql/colexec/colexecprojconst/proj_const_left_ops.eg.go:1 — 26,463 lines (183× median) |
| line-count | pkg/sql/parser/sql.y:1 — 20,836 lines (144× median) |
| line-count | pkg/sql/colexec/colexecjoin/mergejoiner_fullouter.eg.go:1 — 15,479 lines (107× median) |
| line-count | pkg/sql/colexec/colexecbase/cast.eg.go:1 — 15,261 lines (105× median) |
| line-count | pkg/sql/colexec/colexecjoin/mergejoiner_exceptall.eg.go:1 — 14,325 lines (99× 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 · strong · ratings ↑No finding. 16 checks ran and none fired; the rejection log below says why each did not.
Organization & Key-Person Risk
03 · strong · ratings ↑No finding. 10 checks ran and none fired; the rejection log below says why each did not.
Product & Engineering Maturity
04 · adequate · ratings ↑216 direct dependencies in a single manifest
adequate worth checking firstgo.mod declares 216 direct dependencies. Each one is a maintenance obligation, a supply-chain surface and a potential licence question that transfers with the asset. The count says nothing about whether any given dependency was a good choice; it says how many such choices a buyer inherits.
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 go.mod and the 3 other files it cites settles it. If it holds when someone checks it, this finding is significant.
| direct-dependencies | go.mod — 216 declared |
| direct-dependencies | pkg/ui/workspaces/db-console/package.json — 56 declared |
| direct-dependencies | pkg/ui/workspaces/cluster-ui/package.json — 42 declared |
| direct-dependencies | pkg/ui/package.json — 10 declared |
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.
Node.js 16 is past end of life
adequateThe code is pinned to Node.js 16 (end of life 2023-09-11). None of these receives security fixes any more; the first stopped on 2023-09-11. Moving off an unsupported runtime is rarely a one-line change, so a buyer should ask whether the upgrade is planned and what it touches.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| .node-version | .node-version — Node.js 16, end of life 2023-09-11 |
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.
Releases are cut from another branch than the one surveyed
adequateThe newest release, v26.2.9, is not on the branch this survey read; the newest pre-release on it is v26.2.0-alpha.2. The shipped product may differ from what this report describes. Survey the release branch too. This was read from the most recent 50,000 commits (1 Apr 2022 to 23 Sep 2026) only; older history was not read.
A note that does not affect this rating: notes like it are common in well-run projects.
| 7b4e548e3 | tag v26.2.9 |
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 ↑3 Dockerfiles run the application as root
adequateNo USER instruction switches away from root, so the process runs with full privileges inside the container. It is a one-line fix and an ordinary expectation, which is why its absence is worth asking about: it usually says more about whether anyone has reviewed the deployment than about this container specifically.
| no-USER-instruction | pkg/cmd/roachprod-centralized/docker/Dockerfile — runs as root |
| no-USER-instruction | pkg/cmd/roachprod/docker/Dockerfile — runs as root |
| no-USER-instruction | pkg/cmd/roachtest/dlq-replay/Dockerfile — runs as root |
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.
133 SQL statements built from strings
adequate worth checking first133 places in product code build SQL by formatting or joining strings rather than passing parameters, and in 5 of them a value, not a table or column name, goes into the string. Where any of those values comes from a request, it is an injection point. Each site needs a look; the fix, parameters, is small.
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 pkg/cli/node.go:246 and the 1 other file it cites settles it. If it holds when someone checks it, this finding is significant.
| pkg/cli/node.go | pkg/cli/node.go:246 — SQL built from a string |
| pkg/jobs/registry.go | pkg/jobs/registry.go:1213 — SQL built from a string |
| pkg/jobs/registry.go | pkg/jobs/registry.go:1303 — SQL built from a string |
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.
108 locked dependencies have published vulnerabilities, 23 high or critical in what ships
adequate worth checking first108 of 2,967 locked dependencies match 175 published advisories in OSV, 101 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. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
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 go.mod and the 1 other file it cites settles it. If it holds when someone checks it, this finding is significant.
| go.mod | go.mod — github.com/jackc/pgx/v5 v5.7.2: GHSA-9jj7-4m8r-rfcm (critical), fixed in 5.9.0 |
| go.mod | go.mod — golang.org/x/crypto v0.50.0: GHSA-5cgq-3rg8-m6cv (critical), fixed in 0.52.0 |
| pkg/ui/pnpm-lock.yaml | pkg/ui/pnpm-lock.yaml — @babel/traverse 7.22.6: GHSA-67hx-6x53-jw92 (critical), fixed in 7.23.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 workload settings give a container the host
adequate worth checking first4 places in the deployment configuration run a container privileged or in the host's network, process or IPC namespace. A compromise of that container is a compromise of the machine, and most acquirers' security reviews block it. Node agents (network, storage, monitoring) are excluded.
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 cloud/kubernetes/performance/cockroachdb-daemonset-insecure.yaml:81 and the 2 other files it cites settles it. If it holds when someone checks it, this finding is significant.
| cloud/kubernetes/performance/cockroachdb-daemonset-insecure.yaml | cloud/kubernetes/performance/cockroachdb-daemonset-insecure.yaml:81 — privileged or host namespace |
| cloud/kubernetes/performance/cockroachdb-daemonset-secure.yaml | cloud/kubernetes/performance/cockroachdb-daemonset-secure.yaml:153 — privileged or host namespace |
| cloud/kubernetes/performance/cockroachdb-statefulset-insecure.yaml | cloud/kubernetes/performance/cockroachdb-statefulset-insecure.yaml:121 — privileged or host namespace |
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.
The production build publishes source maps
adequateThe build configuration emits source maps for production, so the original source, with its comments and structure, is downloadable by every visitor. Upload them to an error tracker and keep them off the public server instead.
| pkg/ui/workspaces/cluster-ui/webpack.config.js | pkg/ui/workspaces/cluster-ui/webpack.config.js:39 — source maps in a production build |
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.
Licence text does not match a standard licence
adequateLICENSE exists but its text does not match any standard licence. A bespoke or hand-edited licence is not wrong, but it cannot be cleared by recognising its name: counsel has to read it, and until they do neither side knows precisely what rights transfer with the code.
| LICENSE | LICENSE:1 — 166 lines, unrecognised |
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.
The build runs third-party code it does not pin
adequate5 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day. Tags have been moved to malicious commits in real supply-chain attacks, and a piped script is whatever the server returns that minute. Pinning to a commit is the fix, and it is small.
A note that does not affect this rating: notes like it are common in well-run projects.
| .github/workflows/blathers-backport.yml | .github/workflows/blathers-backport.yml:44 — action pinned by tag |
| .github/workflows/blathers-backport.yml | .github/workflows/blathers-backport.yml:264 — action pinned by tag |
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.
6 outbound calls can wait forever
adequate6 HTTP calls use a client with no timeout (Python `requests` without `timeout=`, or Go's default client). When a dependency slows down, each one holds a worker until the connection gives up, and enough of them take the service down with the dependency.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| pkg/ccl/changefeedccl/kafkaauth/sasl_proprietary_oauth.go | pkg/ccl/changefeedccl/kafkaauth/sasl_proprietary_oauth.go:119 — outbound call without a timeout |
| pkg/cmd/bazci/bazci.go | pkg/cmd/bazci/bazci.go:312 — outbound call without a timeout |
| pkg/cmd/dev/util.go | pkg/cmd/dev/util.go:237 — outbound call without a timeout |
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 of 14 Kubernetes workloads declare no resource limits
adequate4 workload manifests set no CPU or memory limits. One pod that leaks memory or spins can starve everything else on its node, and the scheduler cannot plan capacity for what it cannot see.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| cloud/kubernetes/example-app-secure.yaml | cloud/kubernetes/example-app-secure.yaml — workload with no limits |
| cloud/kubernetes/example-app.yaml | cloud/kubernetes/example-app.yaml — workload with no limits |
| cloud/kubernetes/multiregion/cockroachdb-statefulset-secure.yaml | cloud/kubernetes/multiregion/cockroachdb-statefulset-secure.yaml — workload with no limits |
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.
Relicensed: Apache-2.0 → BUSL-1.1 (2019-06-04)
adequateThe root licence changed 1 time(s). The latest terms restrict what users, hosts or a buyer may do in ways the earlier ones did not. Code taken under the old terms stays under them, so both matter in diligence.
A note that does not affect this rating: a licence change is a fact for the first screen, and only a narrowing of rights within two years of the surveyed commit costs "strong".
| 854898781 | LICENSE — Apache-2.0 from 2014-02-06 |
| 8acfe8ffd | LICENSE — BUSL-1.1 from 2019-06-04 |
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 stats.stackexchange.com by default
adequatepkg/sql/opt/memo/statistics_builder.go sends to stats.stackexchange.com, and pkg/server/status.go 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.
| pkg/sql/opt/memo/statistics_builder.go | pkg/sql/opt/memo/statistics_builder.go:4935 — reports to stats.stackexchange.com |
| pkg/server/status.go | pkg/server/status.go:4777 — 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.
1 of 5 deployed images carry no version, or `latest`
adequate1 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.
A note that does not affect this rating: in Borehole's calibration, this check's notes were usually true but overstated.
| cloud/kubernetes/v1.20/cockroachdb-statefulset.yaml | cloud/kubernetes/v1.20/cockroachdb-statefulset.yaml:100 — image without a version |
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
10 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 (docs/RFCS/20191014_savepoints/distsender.puml and 23 more). Does it match what the team believes today? Ask them to walk through it against the code.
- measured The repository pulls code in through git submodules (.gitmodules). A buyer receives pointers, not that code. Can every submodule be fetched without the team's credentials, and who owns each one?
- 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 coverage- measured 420 people have committed here. Which of them are you acquiring, and which are you replacing?
- 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- measured No threat model is in the tree of what looks like a running service. Does one exist elsewhere, and who owns it?
- measured Infrastructure code (pkg/roachprod/vm/aws/terraform/aws-region/ami.tf and 5 more) last changed 24 months before the newest commit, while 13,759 commits landed. Is the infrastructure now changed by hand? Compare the live account with the code.
- 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- measured Backup or restore tooling is in the tree (build/teamcity/cockroach/nightlies/sqllogic_backup_restore.sh). Has a restore ever been rehearsed, and how long did it take?
- measured Alert rules are defined in the repository. Who receives them, and when did one last fire?
- 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 Go codebase. Does your engineering organisation already run Go in production, or would this be the first?
- The bulk of this system sits in pkg/, licenses/, build/. Which of your existing systems would each of those have to absorb or replace?
- The repository carries deployment configuration (build/bazelbuilder/Dockerfile and 17 more). Does that match your deployment and on-call model, or does it need rehosting first?
- 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/cockroachdb/cockroach/d30c905)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 — 88 signals that ran and did not fire
Appendix: rejection log — 88 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 files, in the most recent 50,000 commits (1 Apr 2022 to 23 Sep 2026)files 28,838 · top5 share 0.015 · history read the most recent 50,000 commits (1 Apr 2022 to 23 Sep 2026) |
| 04.debt_markers | debt markers are sparsemarkers 4,824 · per kloc 2.04 · lines read 2,363,581 |
| 04.test_growth | test effort kept pace with code written, in the most recent 50,000 commits (1 Apr 2022 to 23 Sep 2026)history read the most recent 50,000 commits (1 Apr 2022 to 23 Sep 2026) · late test per code 0.797 · early test per code 0.655 |
| 04.churn_trend | rework is not rising against new work, in the most recent 50,000 commits (1 Apr 2022 to 23 Sep 2026)history read the most recent 50,000 commits (1 Apr 2022 to 23 Sep 2026) · late delete per insert 0.524 · early delete per insert 0.548 |
| 04.fixes_with_tests | fixes usually come with a testfixes 1,298 · share 0.675 · with tests 876 |
| 04.fix_share_trend | fixing is not crowding out building |
| 04.compat_layers | little code is kept for the old wayshare 0.001 · code files 6,810 · compat files 6 |
| 04.dependency_redundancy | one library per job, mostly |
| 06.telemetry_presence | a telemetry or error-reporting library is referencednote presence only; whether anyone watches it is not visible here · matches 112 |
| 06.structured_logging | a structured logging library is referencedmatches 31 |
| 06.healthcheck_presence | a health or readiness check is defined |
| 06.telemetry_depth | the service is visible in more than one way |
| 06.correlation_ids | a request can be followed through the logstracing True · request id sites 62 |
| 06.error_reporting | an error reporter is initialisedinitialised 1 · config files 0 |
| 06.alert_rules | alert rules are defined as codealert files 3 |
| 06.single_replica | an autoscaler or disruption budget is definedworkloads 12 |
| 06.environment_branching | environment differences live in configurationsites 0 |
| 06.release_markers | releases are markedtags last year 126 · release commits 29 · changelog commits 10 |
| 06.migrate_on_start | migrations do not run at container start |
| 03.contributor_concentration | no single contributor dominates the last 24 monthswindow last 24 months · authors 420 · top share less than a quarter |
| 03.critical_path_ownership | more than one person changes the critical pathsauthors 208 |
| 03.second_contributor_attrition | the second and third contributors are still active |
| 03.bus_factor_trend | the team has not narrowed to one person |
| 03.joiners_and_leavers | the team is not shrinkingleft 34 · joined 21 · regular last year 90 |
| 02.merge_discipline | a meaningful share of recent change carries evidence of reviewmerges 7,469 · window last 24 months · with tracked 5,734 |
| 02.ci_presence | CI configuration is present in the working treecount 27 |
| 02.test_presence | tests are present in a normal proportion to sourcetests 4,148 · source 10,351 · test ratio 0.401 |
| 02.conventional_commits | commit subjects generally carry content, in the most recent 50,000 commits (1 Apr 2022 to 23 Sep 2026)sampled 33,619 · history read the most recent 50,000 commits (1 Apr 2022 to 23 Sep 2026) · low content share 0.0 |
| 02.branch_protection_hints | process scaffolding is present in the repository |
| 02.ci_runs_tests | CI invokes a test runnerconfigs 27 · with tests 4 |
| 02.skipped_tests | few tests are switched offfocused 0 · skipped 0 · test files 10,186 |
| 02.ci_test_gating | no test run in CI is written so that it cannot failconfigs 27 |
| 02.revert_share | change is rarely undoneshare 0.005 · reverts 62 · recent commits 13,724 |
| 02.dependency_update_cadence | dependencies move with the codelockfiles 4 · commits since 48 · days since lockfile changed 113 |
| 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 4 · ci configs 27 · product files 6,810 |
| 02.long_lived_branches | the typical branch reaches the trunk quicklyshare 0.047 · merges 7,457 · long lived 349 |
| 02.commit_size | changes arrive in reviewable sizesshare 0.012 · commits 12,318 · over 2000 lines 152 |
| 01.burst_import | no commit run met both the rate and the net-addition threshold, in the most recent 50,000 commits (1 Apr 2022 to 23 Sep 2026)gap seconds 180 · history read the most recent 50,000 commits (1 Apr 2022 to 23 Sep 2026) · min add ratio 3.0 |
| 01.message_uniformity | commit subjects vary in wording and length, in the most recent 50,000 commits (1 Apr 2022 to 23 Sep 2026)history read the most recent 50,000 commits (1 Apr 2022 to 23 Sep 2026) · length stdev 17.7 · repeat share 0.019 |
| 01.duplicated_blocks | little shipping code is repeated verbatim across filesshare 0.0097 · product files 6,228 · distinct blocks 1,257,587 |
| 01.swallowed_errors | errors are rarely thrown awayloc 2,370,315 · files 3 · per kloc 0.0 |
| 01.build_reproducibility | every base image names a versionfloating 0 · from lines 8 |
| 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 6,761 |
| 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_management_pattern | no environment file is committed outside tests and examplesenv files 0 |
| 05.shell_from_strings | product code does not build shell commands from stringssites 1 |
| 05.unsafe_deserialization | no code-executing deserialiser in product codesites 0 |
| 05.credentials_in_deploy_config | deployment configuration references secrets, never holds themfiles 0 · sites 0 |
| 05.signing_material | no signing keystore or profile is committedfiles 0 |
| 05.license_copyleft_inherited | every licence found in vendored code is permissive or weak-copyleftvendored paths 48 |
| 05.license_vendored_unlicensed | no vendored third-party code is committedcomponents 0 |
| 05.committed_native_libraries | no widely used compiled library is committed to the productlibraries 0 |
| 04.deprecations_lingering | few deprecations have outlived two yearsolder than two years 2 · files with deprecations 17 |
| 04.dependency_churn | few dependencies were added and dropped within 60 daysdependencies seen 349 · added in two years 174 · removed within 60 days 4 |
| 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.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 1 · commits last 90 days 26 |
| 03.single_maintainer | no file says one person maintains itstatements 0 |
Could not conclude, or did not apply — 23
Not a clean result. Each says why it could not answer here.
| Signal | Why |
|---|---|
| 04.schema_churn | no schema migrations to read |
| 06.print_logging | a frontend: console output is the browser's, not the server's |
| 06.probes_identical | readiness and liveness are distinct, or not both set |
| 06.feature_flags | no feature-flag service; flags may live elsewhere |
| 03.active_contributors | not assessed: this check needs the whole history, and only the most recent 50,000 commits (1 Apr 2022 to 23 Sep 2026) were read |
| 03.knowledge_silos | not assessed: this check needs the whole history, and only the most recent 50,000 commits (1 Apr 2022 to 23 Sep 2026) were read |
| 03.drive_by_contributors | not assessed: this check needs the whole history, and only the most recent 50,000 commits (1 Apr 2022 to 23 Sep 2026) were read |
| 03.contributor_attrition | not assessed: this check needs the whole history, and only the most recent 50,000 commits (1 Apr 2022 to 23 Sep 2026) were read |
| 02.release_cadence | not assessed: this check needs the whole history, and only the most recent 50,000 commits (1 Apr 2022 to 23 Sep 2026) were read |
| 01.initial_dump | not assessed: this check needs the whole history, and only the most recent 50,000 commits (1 Apr 2022 to 23 Sep 2026) were read |
| 01.revision_depth | not assessed: this check needs the whole history, and only the most recent 50,000 commits (1 Apr 2022 to 23 Sep 2026) were read |
| 01.notebook_outputs | not a data or machine-learning repository |
| 05.migration_reversibility | too few migrations to judge |
| 05.public_env_secret | not assessed for Go, the language the product is written in: this check's patterns read other languages only |
| 05.unsafe_html | not assessed for Go, the language the product is written in: this check's patterns read other languages only |
| 05.cleartext_traffic | not a mobile app |
| 05.dataset_provenance | not a data or machine-learning repository |
| 05.license_manifest_conflict | no packaging manifest states a licence |
| 04.flags_accumulating | few or no feature flags in the history |
| 04.api_versions_coexisting | one API version is served, or none |
| 05.project_advisories | record incomplete: no advisory found in the sources that answered; OSV Go github.com/cockroachdb/cockroach (an empty record for a package published here), OSV npm @cockroachlabs/cluster-ui (an empty record for a package published here), OSV npm @cockroachlabs/crdb-protobuf-client (an empty record for a package published here) did not; NVD: 1 record names cockroach with nothing tying it to this repository (CVE-2025-9276) |
| 05.advisory_record | record incomplete: no advisory against the project in the last 24 months; OSV Go github.com/cockroachdb/cockroach (an empty record for a package published here), OSV npm @cockroachlabs/cluster-ui (an empty record for a package published here), OSV npm @cockroachlabs/crdb-protobuf-client (an empty record for a package published here) did not answer; NVD: 1 record names cockroach with nothing tying it to this repository (CVE-2025-9276) |
| 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 EZ00-KVY4-XN6F 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/EZ00KVY4XN6F?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: 2616.1authenticated: False |
| 197.4s | cloned the repository to a temporary directory | depth: full |
| 279.5s | read the git history | commits: 50000tracked files: 20517 |
| 895.0s | ran the deterministic checks | blame pass: Falseread working tree: False |
| 895.1s | recorded where this scan ran | attested: Falseenvironment: cloud-run |
| 1375.0s | kept the facts, never the source, for re-reading under new checks | |
| 1375.0s | deleting the working copy |
Total 1375.0s ·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).