Read 2026-11-03
hledgerorg/hledger: technical due diligence, read from its repository
What Borehole read in hledgerorg/hledger's code and history at 2a7b746: 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 | strong |
| 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
.github/pull_request_template.md:5: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
stronghledger-lib/Hledger/Data/Lots.hs is 3,045 lines, 54× this codebase's median file
adequateThe median source file here is 56 lines. 18 files exceed 1,000 lines, the largest being 3,045. 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.
hledger-lib/Hledger/Data/Lots.hs:1 — 3,045 lines (54× median) |
hledger-web/Hledger/Web/Test.hs:1 — 2,821 lines (50× median) |
hledger-lib/Hledger/Read/RulesReader.hs:1 — 2,660 lines (47× median) |
hledger-lib/Hledger/Read/Common.hs:1 — 2,503 lines (44× median) |
hledger/shell-completion/hledger-completion.bash:1 — 2,205 lines (39× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongEffort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.63 to 0.82 between the first and second halves of this history. Rework is normal and often healthy, but a rising ratio means an increasing share of the team's time is spent replacing code that already exists rather than building what does not. Whether that is deliberate repayment or churn is a question for the team.
| first half 0.63, second half 0.82 (split 2016-12-15) |
Releases are cut from another branch than the one surveyed
adequateThe newest release, 1.99.6, is not on the branch this survey read; the newest release on it is 1.51.99. The shipped product may differ from what this report describes. Survey the release branch too.
| tag 1.99.6 |
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 1,794 tracked files; 0 present |
2 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.
Dockerfile — runs as root |
docker-arm32v7/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate6 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day; 2 steps pipe a download straight into a shell. Tags have been moved to malicious commits in real supply-chain attacks, and a piped script is whatever the server returns that minute. Pinning to a commit is the fix, and it is small.
.github/workflows/_binaries-linux-arm32v7.yml:17 — action pinned by tag |
.github/workflows/_binaries-linux-arm32v7.yml:20 — action pinned by tag |
.github/workflows/_binaries-linux-arm64-stack.yml:142 — download piped into a shell |
2 advisories against this project in the last 24 months, 2 high or critical
adequateThe newest was published on 2026-08-27. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 2 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 1.51.99. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 1 record names hledger with nothing tying it to this repository (CVE-2021-46888).
| 2026-08-27: GHSA-vq7r-8w52-jv84 (high), fixed in 1.52.3: hledger-web: cross-site scripting in the add form, and journal file injection via submitted newlines |
| 2026-08-24: GHSA-538p-cvc4-4qjm (high), fixed in 1.52.2: XSS via unsanitized add-form autocomplete suggestions in hledger-web |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 626 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 626 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 |
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 hledgerorg/hledger: 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.