Borehole · Project · free tier
git.sr.ht/~rjarry/aerc
Free reading: not for reliance
0d169b7 · 3,018 commits · 620 files
Read 2026-10-04

git.sr.ht/~rjarry/aerc: technical due diligence, read from its repository

What Borehole read in git.sr.ht/~rjarry/aerc's code and history at 0d169b7: 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.

DimensionRating
Architecture & Codebase — including AI provenancestrong
Engineering Process & SDLC Maturitystrong
Product & Engineering Maturityadequate
Security & Reliability Posturestrong
Observability & Operationsadequate
Fit with the Acquirernot assessable

Architecture & Codebase — including AI provenance

strong
01.6

app/compose.go is 2,027 lines, 22× this codebase's median file

adequate

The median source file here is 89 lines. 7 files exceed 1,000 lines, the largest being 2,027. 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.

Evidence
app/compose.go:1 — 2,027 lines (22× median)
lib/msgstore.go:1 — 1,109 lines (12× median)
worker/notmuch/worker.go:1 — 1,100 lines (12× median)
app/aerc.go:1 — 1,094 lines (12× median)
filters/colorize.c:1 — 1,029 lines (11× median)

Engineering Process & SDLC Maturity

strong

No finding.

Product & Engineering Maturity

adequate
04.19

9% of bug fixes add or change a test

adequate

Of 91 fixes in the last 24 months, 8 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.

Evidence
8 of 91

Security & Reliability Posture

strong
05.13

2 outbound calls can wait forever

adequate

2 HTTP calls use a client with no timeout (Python `requests` without `timeout=`, or Go's default client). When a dependency slows down, each one holds a worker until the connection gives up, and enough of them take the service down with the dependency.

Evidence
commands/account/import-mbox.go:135 — outbound call without a timeout
commands/msg/unsubscribe.go:225 — outbound call without a timeout
05.21

16 shell commands built from strings

adequate

16 places run a command through a shell (`shell=True`, `os.system`, `exec` with a template) rather than passing arguments. Where any part comes from outside, it is command injection. Ask where each one's input comes from.

Evidence
app/compose.go:1885 — command run through a shell
app/msgviewer.go:500 — command run through a shell
app/msgviewer.go:517 — command run through a shell

Observability & Operations

adequate
06.1

No telemetry or error reporting is wired in anywhere

adequate

None of 446 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.

Evidence
searched 446 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
06.2

No structured logging library is in use

adequate

Nothing 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.

Evidence
searched 446 files for 10 structured logging libraries; 0 matched
06.8

One request cannot be followed through the logs

adequate

Nothing 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.

Evidence
no request id, correlation id or tracing found
06.9

No error reporter is wired in

adequate

Nothing 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.

Evidence
no error reporter initialised

Fit with the Acquirer

not assessable

Not rated: structurally not assessable from a repository.

Read more, or read your own

The full report on git.sr.ht/~rjarry/aerc: 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.