Read 2026-10-04
vim/vim: technical due diligence, read from its repository
What Borehole read in vim/vim's code and history at 4505de4: 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 | adequate |
| Engineering Process & SDLC Maturity | strong |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
.github/pull_request_template.md:54: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
adequatesrc/evalfunc.c is 13,097 lines, 176× this codebase's median file
adequateThe median source file here is 74 lines. 265 files exceed 1,000 lines, the largest being 13,097. 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/evalfunc.c:1 — 13,097 lines (176× median) |
src/testdir/test_vim9_class.vim:1 — 12,090 lines (163× median) |
runtime/keymap/korean-dubeolsik_utf-8.vim:1 — 11,238 lines (151× median) |
src/ex_docmd.c:1 — 10,631 lines (143× median) |
src/os_win32.c:1 — 9,745 lines (131× median) |
1 model weight file committed directly to git
adequate1 model weight files are stored in git itself, not in LFS, DVC or a model hub. Every clone carries them, the history keeps every version for good, and nothing records which run or data produced them.
runtime/tutor/tutor1.pt — weights in git |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate0% of bug fixes add or change a test
adequateOf 259 fixes in the last 24 months, 0 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.
| 0 of 259 |
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.
runtime/syntax/testdir/input/dockerfile.dockerfile — runs as root |
The build runs third-party code it does not pin
adequate5 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. 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/ci-cygwin.yml:67 — action pinned by tag |
.github/workflows/ci-linux.yml:120 — action pinned by tag |
Licence text does not match a standard licence
adequateLICENSE exists but its text does not match any standard licence. A bespoke or hand-edited licence is not wrong, but it cannot be cleared by recognising its name: counsel has to read it, and until they do neither side knows precisely what rights transfer with the code.
LICENSE:1 — 78 lines, unrecognised |
62 advisories against this project in the last 24 months, 4 high or critical
adequateThe newest was published on 2026-09-12. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. None of them affects the surveyed version.
| 2026-09-12: GHSA-x9jf-rjm6-vxqh (low), fixed in v9.2.1090: Ex Command Injection in sign_jump() in Vim < v9.2.1090 |
| 2026-08-26: GHSA-cvc5-p4x9-3f9f (low), fixed in v9.2.1014: Integer Overflow in Undo File Entry Size Check in Vim < v9.2.1014 && Vim >= v8.1.0688 |
| 2026-08-26: GHSA-vfc7-mhvm-gjp8 (moderate), fixed in v9.2.1013: Out-of-bounds Access in libvterm Resize Handling in Vim < 9.2.1013 |
| 2026-08-25: GHSA-r77m-8m55-rpr6 (moderate), fixed in v9.2.1011: Ex Command Injection via Unescaped '|' in tagfiles() Path (ccomplete.vim StructMembers) |
| 2026-07-24: GHSA-r22p-fhw4-84p2 (moderate), fixed in v9.2.0847: Arbitrary Command Execution via Malicious `.VimballRecord` Entry Replay in `vimball.vim` |
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 vim/vim: 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.