Read 2026-10-04
git.sr.ht/~xenrox/hut: technical due diligence, read from its repository
What Borehole read in git.sr.ht/~xenrox/hut's code and history at ed57f11: 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 | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongtodo.go is 2,785 lines, 15× this codebase's median file
adequateThe median source file here is 181 lines. 1 file exceed 1,810 lines, the largest being 2,785. 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.
todo.go:1 — 2,785 lines (15× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate1 test files against 51 source files (2.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.
| 1 test files / 51 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 — none are present. 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.
| 0 of 5 markers present across 82 tracked files |
Product & Engineering Maturity
strongChange keeps returning to the same few files
adequateFive files out of 87 absorb 33% 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.
doc/hut.1.scd — 255 commits touched it |
git.go — 133 commits touched it |
todo.go — 124 commits touched it |
builds.go — 105 commits touched it |
lists.go — 96 commits touched it |
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 82 tracked files; 0 present |
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 git.sr.ht/~xenrox/hut: 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.