Read 2026-11-03
databendlabs/databend: technical due diligence, read from its repository
What Borehole read in databendlabs/databend's code and history at c471f50: 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
LICENSE: Relicensed: Apache-2.0 → AGPL-3.0 (2020-10-14) → Apache-2.0 (2021-02-15) → Elastic-2.0 (2023-04-28) → Apache-2.0 (2026-10-15)src/meta/ee/Cargo.toml: 41 files are named as enterprise-edition codeAGENTS.md:32: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongsrc/meta/schema-api-test-suite/src/schema_api_test_suite.rs is 10,512 lines, 89× this codebase's median file
adequateThe median source file here is 117 lines. 99 files exceed 1,170 lines, the largest being 10,512. 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.
src/meta/schema-api-test-suite/src/schema_api_test_suite.rs:1 — 10,512 lines (89× median) |
src/query/ast/src/parser/statement.rs:1 — 7,185 lines (61× median) |
src/query/config/src/config.rs:1 — 4,308 lines (36× median) |
src/query/service/src/interpreters/access/privilege_access.rs:1 — 3,705 lines (31× median) |
src/query/functions/src/scalars/variant.rs:1 — 3,626 lines (30× median) |
Engineering Process & SDLC Maturity
adequate8% of recent commits change more than 2,000 lines
adequate205 of 2615 commits in the last 24 months changed over 2,000 lines of code, not counting reformatting, renames, vendored or generated code. A change that size is rarely reviewed line by line. Ask how they were reviewed, and what made them that large.
| 205 commits over 2,000 lines |
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest pre-release, v1.2.911-rc6, is not on the branch this survey read; the newest release on it is v1.2.881. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v1.2.911-rc6 |
Security & Reliability Posture
adequate6 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.
.oss-scanner/Dockerfile — runs as root |
docker/Dockerfile — runs as root |
docker/build-tool/debian/Dockerfile — runs as root |
docker/build-tool/dev/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate11 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; 2 steps pipe a download straight into a shell. 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.
.github/workflows/build_tool.yml:33 — action pinned by tag |
.github/workflows/cloud.yml:155 — action pinned by tag |
scripts/ci/ci-setup-chaos-meta.sh:53 — download piped into a shell |
52 locked dependencies have published vulnerabilities, 13 high or critical
adequate52 of 1,434 locked dependencies match 101 published advisories in OSV, 13 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. None of the high or critical ones is in what the product ships: they are optional extras of a package, installed only on request. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
Cargo.lock — wasmtime 27.0.0: GHSA-897f-g5gm-fmxm (critical), fixed in 36.0.19 |
Cargo.lock — zip 4.6.1: GHSA-m665-v7pm-7grj (critical), fixed in 9.0.5 |
src/bendpy/uv.lock — pyarrow 21.0.0: GHSA-rgxp-2hwp-jwgg (high), fixed in 23.0.1; an optional extra |
Relicensed: Apache-2.0 → AGPL-3.0 (2020-10-14) → Apache-2.0 (2021-02-15) → Elastic-2.0 (2023-04-28) → Apache-2.0 (2026-10-15)
adequateThe root licence changed 4 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.
41 files are named as enterprise-edition code
adequateFiles named `.ee.` are, by the common open-core convention, the paid edition's code, usually under a licence that is not open source even where the rest is. What the buyer may do with each part differs.
src/meta/ee/Cargo.toml — enterprise-edition file |
src/meta/ee/src/lib.rs — enterprise-edition file |
src/query/ee/Cargo.toml — enterprise-edition file |
Observability & Operations
adequateOne request cannot be followed through the logs
adequateNothing in the service carries a request or correlation id, and there is no tracing. When a customer reports a failure, the log lines that belong to their request cannot be picked out from everyone else's.
| no request id, correlation id or tracing found |
No error reporter is wired in
adequateNothing in the service initialises an error reporter (Sentry, Rollbar, Bugsnag, Honeybadger or an APM agent). An exception in production reaches a person only if someone is reading the logs, which usually means a customer reports it first.
| no error reporter initialised |
Has a reporting host, telemetry.databend.com; its default could not be read
adequatesrc/common/building/src/lib.rs names telemetry.databend.com as a place to report to, and no setting read here shows whether reporting is on as shipped. For a buyer running it inside their own product, ask whether copies report by default, what is sent, how often, and whether the buyer's customers were told.
src/common/building/src/lib.rs:130 — names telemetry.databend.com |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on databendlabs/databend: 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.