Read 2026-10-04
ghostty-org/ghostty: technical due diligence, read from its repository
What Borehole read in ghostty-org/ghostty's code and history at 4da7523: 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 | strong |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
AI_POLICY.md:1: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongsrc/terminal/PageList.zig is 20,543 lines, 168× this codebase's median file
adequateThe median source file here is 122 lines. 73 files exceed 1,220 lines, the largest being 20,543. 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/PageList.zig:1 — 20,543 lines (168× median) |
src/terminal/Terminal.zig:1 — 16,740 lines (137× median) |
src/terminal/Screen.zig:1 — 12,645 lines (103× median) |
src/config/Config.zig:1 — 11,317 lines (92× median) |
src/stb/stb_image.h:1 — 7,988 lines (65× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate2% of bug fixes add or change a test
adequateOf 944 fixes in the last 24 months, 18 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.
| 18 of 944 |
Security & Reliability Posture
strongThe build runs third-party code it does not pin
adequate1 third-party CI action is referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day; 4 steps pipe a download straight into a shell. 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/release-tag.yml:147 — action pinned by tag |
.github/workflows/release-tag.yml:299 — download piped into a shell |
4 vendored components with no licence
adequateThird-party code is committed into this repository without any statement of the terms it arrived under. Unknown terms are harder to deal with than inconvenient ones: an awkward licence can be complied with, an absent one cannot. Each of these needs its origin established before the code changes hands.
pkg/breakpad/vendor/third_party — 1 tracked files, no licence file |
pkg/simdutf/vendor/simdutf.cpp — 1 tracked files, no licence file |
pkg/simdutf/vendor/simdutf.h — 1 tracked files, no licence file |
src/shell-integration/nushell/vendor/autoload — 1 tracked files, no licence file |
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 ghostty-org/ghostty: 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.