Read 2026-11-03
kaelio/ktx: technical due diligence, read from its repository
What Borehole read in kaelio/ktx's code and history at 49a4ae6: 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 | adequate |
| 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
CONTRIBUTING.md:65: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
adequateThe repository begins with most of itself already written
adequateThe first commit carries 257,054 lines — 45% of every line ever added. Whatever happened before that commit happened somewhere this repository cannot show you, so the early history is not available as evidence of how the system was designed.
| 2026-05-10T21:12:26+00:00; +257,054 across 1199 files; subject: 'Initial open-source release' |
packages/cli/src/context/ingest/ingest-bundle.runner.ts is 3,347 lines, 26× this codebase's median file
adequateThe median source file here is 125 lines. 9 files exceed 1,250 lines, the largest being 3,347. 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.
packages/cli/src/context/ingest/ingest-bundle.runner.ts:1 — 3,347 lines (26× median) |
packages/cli/src/setup-databases.ts:1 — 2,618 lines (20× median) |
packages/cli/src/setup-sources.ts:1 — 2,331 lines (18× median) |
packages/cli/src/context/sl/semantic-layer.service.ts:1 — 1,675 lines (13× median) |
python/ktx-sl/semantic_layer/planner.py:1 — 1,476 lines (11× median) |
Engineering Process & SDLC Maturity
adequate9% of recent commits change more than 2,000 lines
adequate37 of 426 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.
| 37 commits over 2,000 lines |
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate5 SQL statements built from strings
adequate5 places in product code build SQL by formatting or joining strings rather than passing parameters. In each, what the code shows going in is a table or column name, a constant, or something the line does not show, not a request's value. Ask whether any value reaches these strings, rather than a parameter.
packages/cli/src/connectors/duckdb/connector.ts:309 — SQL built from a string |
packages/cli/src/connectors/duckdb/connector.ts:319 — SQL built from a string |
packages/cli/src/connectors/duckdb/connector.ts:354 — SQL built from a string |
37 locked dependencies have published vulnerabilities, 43 high or critical in what ships
adequate37 of 1,407 locked dependencies match 129 published advisories in OSV, 57 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.
uv.lock — anyio 4.13.0: GHSA-82r6-8w77-94w6 (critical), fixed in 4.14.2 |
uv.lock — certifi 2026.5.20: GHSA-6q48-6c7w-9gw2 (critical), fixed in 2026.10.18 |
pnpm-lock.yaml — handlebars 4.7.9: GHSA-8r5x-fm3f-whwj (critical), fixed in 4.7.10 |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 1,614 readable files references an instrumentation, metrics or error-reporting library. If this system is in production, nobody learns that it broke from the system itself — they learn it from a customer. That is a reliability finding before it is an observability one.
| searched 1,614 tracked text files for 16 known instrumentation libraries; manifests for metrics, tracing and error-reporting families; locked dependencies for the packages that emit; 0 matched |
One 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 |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on kaelio/ktx: 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.