Read 2026-10-04
jesseduffield/lazygit: technical due diligence, read from its repository
What Borehole read in jesseduffield/lazygit's code and history at a82c0d0: 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
CONTRIBUTING.md:5: The project does not take pull requestsCONTRIBUTING.md:14: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongpkg/i18n/english.go is 2,365 lines, 34× this codebase's median file
adequateThe median source file here is 69 lines. 8 files exceed 1,000 lines, the largest being 2,365. 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.
pkg/i18n/english.go:1 — 2,365 lines (34× median) |
pkg/gocui/view.go:1 — 2,352 lines (34× median) |
pkg/gocui/gui.go:1 — 2,158 lines (31× median) |
pkg/gui/controllers/local_commits_controller.go:1 — 2,025 lines (29× median) |
pkg/gui/controllers/helpers/refresh_helper.go:1 — 1,948 lines (28× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongGo 1.25 is past end of life
adequateThe code is pinned to Go 1.25 (end of life 2026-08-11). None of these receives security fixes any more; the first stopped on 2026-08-11. Moving off an unsupported runtime is rarely a one-line change, so a buyer should ask whether the upgrade is planned and what it touches.
Dockerfile — Go 1.25, end of life 2026-08-11 |
12 files still carry code deprecated more than two years ago
adequate12 files were marked deprecated over two years ago and still are, the oldest since Aug 2018. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.
vendor/golang.org/x/text/transform/transform.go — deprecated since Aug 2018 |
vendor/golang.org/x/sys/windows/security_windows.go — deprecated since Nov 2019 |
vendor/golang.org/x/sys/windows/syscall_windows.go — deprecated since Nov 2019 |
vendor/golang.org/x/sys/unix/zsysnum_darwin_amd64.go — deprecated since Apr 2021 |
vendor/golang.org/x/sys/unix/zsysnum_darwin_arm64.go — deprecated since Apr 2021 |
Security & Reliability Posture
adequate1 Dockerfile runs 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 |
2 outbound calls can wait forever
adequate2 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.
pkg/updates/updates.go:268 — outbound call without a timeout |
pkg/updates/updates.go:321 — outbound call without a timeout |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 1,297 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 1,297 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 jesseduffield/lazygit: 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.