Read 2026-10-23
kritt-ai/open-kritt: technical due diligence, read from its repository
What Borehole read in kritt-ai/open-kritt's code and history at 7658d97: 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 | strong |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
adequateThe repository begins with most of itself already written
adequateThe first commit carries 71,494 lines — 68% 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-07-20T20:27:05+00:00; +71,494 across 340 files; subject: 'feat: first open-source commit' |
executor-view/server.py is 4,854 lines, 45× this codebase's median file
adequateThe median source file here is 106 lines. 12 files exceed 1,060 lines, the largest being 4,854. 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.
executor-view/server.py:1 — 4,854 lines (45× median) |
frontend/src/pages/ScanDetail.jsx:1 — 2,963 lines (27× median) |
engine/open_kritt_engine/harnesses.py:1 — 2,454 lines (23× median) |
engine/open_kritt_engine/db.py:1 — 2,114 lines (19× median) |
engine/open_kritt_engine/workspace.py:1 — 1,951 lines (18× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate5 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.
backend/Dockerfile — runs as root |
database/Dockerfile — runs as root |
engine/Dockerfile — runs as root |
executor-view/Dockerfile — runs as root |
1 SQL statement built from strings
adequate1 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.
executor-view/server.py:661 — SQL built from a string |
3 locked dependencies have published vulnerabilities, 4 high or critical in what ships
adequate3 of 142 locked dependencies match 5 published advisories in OSV, 4 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.
backend/package-lock.json — proxy-addr 2.0.7: GHSA-jqcg-44mw-7w3h (critical), fixed in 2.0.8 |
backend/package-lock.json — body-parser 2.3.0: GHSA-27r3-jxmh-p828 (high), fixed in 2.4.0 |
backend/package-lock.json — brace-expansion 5.0.9: GHSA-6j4f-fj2g-mc7p (high), fixed in 5.0.10 |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 344 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 344 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 |
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 kritt-ai/open-kritt: 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.