Read 2026-10-04
codeberg.org/dnkl/foot: technical due diligence, read from its repository
What Borehole read in codeberg.org/dnkl/foot's code and history at cb27717: 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 | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
CONTRIBUTING.md:3: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongrender.c is 5,480 lines, 62× this codebase's median file
adequateThe median source file here is 88 lines. 15 files exceed 1,000 lines, the largest being 5,480. 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.
render.c:1 — 5,480 lines (62× median) |
terminal.c:1 — 4,854 lines (55× median) |
config.c:1 — 4,375 lines (49× median) |
input.c:1 — 3,691 lines (41× median) |
box-drawing.c:1 — 3,451 lines (39× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate1 test files against 109 source files (0.9%). 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.
| 1 test files / 109 source files |
Almost no process scaffolding exists in the repository
adequateOf five ordinary markers — CI workflows, CODEOWNERS, a pull-request template, pre-commit hooks, contribution guidance — 1 is present: contribution guidance. Branch protection itself is a GitHub setting rather than a file, so this is a reading of proxies and not of the rules themselves. What it does establish is that the process is not written down anywhere a new engineer would find it.
| 1 of 5 markers present across 250 tracked files |
Product & Engineering Maturity
adequateChange keeps returning to the same few files
adequateFive files out of 331 absorb 30% of all file-level change. Concentration like this is where debt is usually being serviced rather than repaid: the same code is reopened because it is load-bearing, fragile, or both. A repository cannot tell you which — that is a conversation with the team.
render.c — 796 commits touched it |
terminal.c — 741 commits touched it |
terminal.h — 511 commits touched it |
config.c — 499 commits touched it |
input.c — 476 commits touched it |
2% of bug fixes add or change a test
adequateOf 59 fixes in the last 24 months, 1 touched a test. A fix without the test that would have caught the bug can quietly come back, and the suite never learns from what went wrong.
| 1 of 59 |
Security & Reliability Posture
adequateNone 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 250 tracked files; 0 present |
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 codeberg.org/dnkl/foot: 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.