Read 2026-10-04
duckdb/duckdb: technical due diligence, read from its repository
What Borehole read in duckdb/duckdb's code and history at e5bc7c2: 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 | not assessable |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
AI_POLICY.md:1: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongsrc/include/duckdb_v2.h is 13,576 lines, 183× this codebase's median file
adequateThe median source file here is 74 lines. 108 files exceed 1,000 lines, the largest being 13,576. 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/include/duckdb_v2.h:1 — 13,576 lines (183× median) |
src/include/duckdb.h:1 — 10,375 lines (140× median) |
src/common/enum_util.cpp:1 — 7,272 lines (98× median) |
src/include/duckdb/parser/peg/transformer/peg_transformer.hpp:1 — 5,778 lines (78× median) |
src/execution/operator/persistent/physical_copy_to_file.cpp:1 — 4,178 lines (56× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate432 test files against 4,340 source files (10.0%). This does not measure whether the tests are good, only whether enough of them exist for the codebase to be changed safely by someone who did not write it — which is exactly the situation after an acquisition.
| 432 test files / 4,340 source files |
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, v1.5.6, is not on the branch this survey read; the newest release on it is v1.5.5. 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 (24 Nov 2023 to 25 Sep 2026) only; older history was not read.
| tag v1.5.6 |
Security & Reliability Posture
not assessableThe build runs third-party code it does not pin
adequate14 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; 4 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/DockerTests.yml:81 — action pinned by tag |
.github/workflows/Main.yml:88 — action pinned by tag |
.github/workflows/Main.yml:1489 — download piped into a shell |
1 vendored component with no licence
adequateThird-party code is committed into this repository without any statement of the terms it arrived under. Unknown terms are harder to deal with than inconvenient ones: an awkward licence can be complied with, an absent one cannot. Each of these needs its origin established before the code changes hands.
third_party/imdb — 4 tracked files, no licence file |
3 advisories against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-08-03. 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 2 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 1.5.5. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 5 records name duckdb with nothing tying them to this repository (CVE-2024-5827, CVE-2024-8099, CVE-2026-41490, …).
| 2026-08-03: CVE-2026-58139 (moderate): The DuckDB AWS extension for DuckDB contains a security policy bypass vulnerability that allows any database user with SQL execution permissions to extract plai |
| 2025-11-12: GHSA-vmp8-hg63-v2hp (moderate), fixed in 1.4.2: Vulnerabilities in DuckDB Encryption Crypto implementation |
| 2025-09-09: CVE-2025-59037 (high): DuckDB is an analytical in-process SQL database management system. On 08 September 2025, the DuckDB distribution for Node.js on npm was compromised with malware |
Observability & Operations
not assessableNot rated: only 4 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 duckdb/duckdb: 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.