Read 2026-10-04
codeberg.org/emersion/soju: technical due diligence, read from its repository
What Borehole read in codeberg.org/emersion/soju's code and history at 3dec1ed: 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 | strong |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
LICENSE: Relicensed: MIT → AGPL-3.0 (2020-02-07)
Architecture & Codebase — including AI provenance
strongdownstream.go is 4,206 lines, 26× this codebase's median file
adequateThe median source file here is 156 lines. 3 files exceed 1,560 lines, the largest being 4,206. 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.
downstream.go:1 — 4,206 lines (26× median) |
upstream.go:1 — 2,620 lines (16× median) |
service.go:1 — 1,793 lines (11× median) |
Engineering Process & SDLC Maturity
strongAlmost 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 94 tracked files |
Product & Engineering Maturity
adequateChange keeps returning to the same few files
adequateFive files out of 135 absorb 54% 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.
downstream.go — 556 commits touched it |
upstream.go — 370 commits touched it |
user.go — 214 commits touched it |
server.go — 152 commits touched it |
service.go — 128 commits touched it |
77 unresolved debt markers, 3.1 per thousand lines
adequateThe codebase carries 77 TODO, FIXME, HACK or XXX markers across 24,812 lines. These are the team's own notes about work they knew was unfinished. A high density is not automatically bad — it can mean an honest team — but every one of them is a decision deferred, and after an acquisition they are deferred onto someone who was not in the room.
auth/oauth2.go:27 — ctx, cancel := context.WithTimeout(context.TODO(), 10*time.Second) |
cmd/soju/main.go:259 — // TODO: this is racy |
cmd/sojudb/main.go:130 — // TODO: the buffering messes up repeated calls to readPassword |
contrib/migrate-db/main.go:126 — // TODO: migrate read receipts as well |
contrib/migrate-logs/main.go:54 — // TODO: switch to ReadDir (Go 1.16+) |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v0.11.1, is not on the branch this survey read; the newest release on it is v0.11.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v0.11.1 |
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 94 tracked files; 0 present |
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.
database/sqlite.go:133 — SQL built from a string |
Relicensed: MIT → AGPL-3.0 (2020-02-07)
adequateThe root licence changed 1 time(s). The latest terms restrict what users, hosts or a buyer may do in ways the earlier ones did not. Code taken under the old terms stays under them, so both matter in diligence.
Observability & Operations
adequateNo structured logging library is in use
adequateNothing references a structured logging library. Logs that are written to be read by a person are not searchable by a machine, which means incident response here is proportional to how well someone remembers the codebase rather than to what the tooling can find.
| searched 87 files for 10 structured logging libraries; 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 codeberg.org/emersion/soju: 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.