Read 2026-10-04
junegunn/fzf: technical due diligence, read from its repository
What Borehole read in junegunn/fzf's code and history at b1be3a8: 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 | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongsrc/terminal.go is 8,851 lines, 68× this codebase's median file
adequateThe median source file here is 129 lines. 6 files exceed 1,290 lines, the largest being 8,851. 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.
src/terminal.go:1 — 8,851 lines (68× median) |
src/options.go:1 — 3,998 lines (30× median) |
src/tui/light.go:1 — 1,698 lines (13× median) |
src/tui/tui.go:1 — 1,528 lines (11× median) |
src/algo/algo.go:1 — 1,342 lines (10× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongChange keeps returning to the same few files
adequateFive files out of 219 absorb 35% 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.
src/terminal.go — 758 commits touched it |
man/man1/fzf.1 — 524 commits touched it |
README.md — 492 commits touched it |
src/options.go — 441 commits touched it |
test/test_go.rb — 357 commits touched it |
Go 1.23 is past end of life
adequateThe code is pinned to Go 1.23 (end of life 2025-08-12). None of these receives security fixes any more; the first stopped on 2025-08-12. 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.
.tool-versions — Go 1.23, end of life 2025-08-12 |
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 |
1 locked dependency has published vulnerabilities
adequate1 of 26 locked dependencies match 1 published advisories in OSV. A lockfile says which version is installed, not whether the flawed code is reachable from this product, so each needs a look. Most are fixed by an upgrade, and the advisory names the version.
go.mod — golang.org/x/sys v0.35.0: GO-2026-5024 (unrated), fixed in 0.44.0 |
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 junegunn/fzf: 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.