Read 2026-10-04
jarun/nnn: technical due diligence, read from its repository
What Borehole read in jarun/nnn's code and history at d1c495b: 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 | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongsrc/nnn.c is 10,994 lines, 144× this codebase's median file
adequateThe median source file here is 76 lines. 2 files exceed 1,000 lines, the largest being 10,994. 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/nnn.c:1 — 10,994 lines (144× median) |
src/icons-in-terminal.h:1 — 3,737 lines (49× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequateChange keeps returning to the same few files
adequateFive files out of 356 absorb 60% 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/nnn.c — 1,976 commits touched it |
README.md — 937 commits touched it |
nnn.1 — 499 commits touched it |
nnn.c — 438 commits touched it |
plugins/README.md — 277 commits touched it |
1% of bug fixes add or change a test
adequateOf 67 fixes in the last 24 months, 1 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.
| 1 of 67 |
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 129 tracked files; 0 present |
Observability & Operations
not assessableNot rated: only 4 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 jarun/nnn: 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.