Read 2026-10-04
helix-editor/helix: technical due diligence, read from its repository
What Borehole read in helix-editor/helix's code and history at 079a789: 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 | not assessable |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
- No release for 12 months while development continues
- Releases are cut from another branch than the one surveyed
Architecture & Codebase — including AI provenance
stronghelix-term/src/commands.rs is 7,229 lines, 328× this codebase's median file
adequateThe median source file here is 22 lines. 22 files exceed 1,000 lines, the largest being 7,229. 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.
helix-term/src/commands.rs:1 — 7,229 lines (328× median) |
helix-term/src/commands/typed.rs:1 — 4,609 lines (209× median) |
helix-lsp-types/src/lib.rs:1 — 2,892 lines (131× median) |
helix-view/src/document.rs:1 — 2,772 lines (126× median) |
helix-view/src/editor.rs:1 — 2,701 lines (122× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate8% of bug fixes add or change a test
adequateOf 336 fixes in the last 24 months, 27 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.
| 27 of 336 |
No release for 12 months while development continues
adequateThe last tag, 25.07.1, was cut 370 days before the survey; the typical gap between releases was 101 days, and 299 commits landed in the last 90 days. Users run the last release, not this code.
| last tag 25.07.1 |
Releases are cut from another branch than the one surveyed
adequateThe newest release, 25.07.1, is not on the branch this survey read; the newest release on it is 25.07. The shipped product may differ from what this report describes. Survey the release branch too.
| tag 25.07.1 |
Security & Reliability Posture
not assessable5 locked dependencies have published vulnerabilities
adequate5 of 337 locked dependencies match 7 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. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
Cargo.lock — crossbeam-epoch 0.9.18: RUSTSEC-2026-0204 (unrated), fixed in 0.9.20 |
Cargo.lock — faster-hex 0.10.0: RUSTSEC-2026-0306 (unrated), fixed in 0.10.1 |
Cargo.lock — memmap2 0.9.10: RUSTSEC-2026-0186 (unrated), fixed in 0.9.11 |
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 helix-editor/helix: 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.