Read 2026-11-03
chdb-io/chdb: technical due diligence, read from its repository
What Borehole read in chdb-io/chdb's code and history at 4fba125: 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 | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongCommit messages are templated rather than written
adequate79% of commit subjects are exact repeats of another subject, and subject length varies by only 28.8 characters. A log written by someone explaining their reasoning to a future reader does not look like this. The log is therefore weak evidence of intent, whatever the code is like.
| 34× 'Update README.md' |
| 26× 'test: test ci' |
| 20× 'Update build_wheels.yml' |
datastore/function_definitions.py is 13,344 lines, 26× this codebase's median file
adequateThe median source file here is 495 lines. 3 files exceed 4,950 lines, the largest being 13,344. 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.
datastore/function_definitions.py:1 — 13,344 lines (26× median) |
datastore/core.py:1 — 9,190 lines (18× median) |
datastore/column_expr.py:1 — 7,113 lines (14× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate6 credential-shaped strings in the tree sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key.
| 5 cited: AWS access key, where fakes are usual |
None of the standard security guard rails are configured
adequateThere is no disclosure policy, no automated dependency updates, no named code owners and no pre-commit configuration. None of these is load-bearing on its own. Their collective absence says that security posture here is whatever the current team happens to remember to do, which is not a posture that survives the team changing.
| checked 5 kinds of guard rail across 577 tracked files; 0 present |
6 dependencies float, and no lockfile is committed
adequateDependency versions are declared as ranges and no lockfile is committed, so a build today does not necessarily produce what a build last month produced. That matters twice over in a transaction: the thing being bought cannot be reproduced exactly, and a compromised upstream release arrives without anyone choosing to take it.
requirements.txt:2 — >=26.7.0 |
requirements.txt:3 — >=2.1.0 |
requirements.txt:4 — >=13.0.0 |
sphinx/requirements.txt:1 — >=1.3 |
sphinx/requirements.txt:2 — any version |
The build runs third-party code it does not pin
adequate5 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_linux_arm64_wheels-gh.yml:41 — download piped into a shell |
Observability & Operations
not assessableNot rated: only 5 of 16 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on chdb-io/chdb: 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.