Read 2026-11-07
gnachman/iterm2: technical due diligence, read from its repository
What Borehole read in gnachman/iterm2's code and history at 7f4ff73: 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 | adequate |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
.gitmodules:1: 19 submodule(s) this survey does not read: submodules/NMSSH, submodules/CoreParse, submodules/Sparkle
Architecture & Codebase — including AI provenance
strongsources/TerminalView/PseudoTerminal.m is 17,139 lines, 171× this codebase's median file
adequateThe median source file here is 100 lines. 166 files exceed 1,000 lines, the largest being 17,139. 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.
sources/TerminalView/PseudoTerminal.m:1 — 17,139 lines (171× median) |
sources/proto/Api.pbobjc.m:1 — 13,962 lines (139× median) |
ThirdParty/ProtobufRuntime/GPBDictionary.m:1 — 12,151 lines (121× median) |
sources/TerminalView/PTYTab.m:1 — 9,591 lines (95× median) |
ThirdParty/SFSymbolEnum/SFSymbolEnum.m:1 — 9,251 lines (92× median) |
Engineering Process & SDLC Maturity
adequateLittle of the recent change carries a trace of review
adequateIn the last 24 months, 175 of 3,550 commits (4.9%) carry any trace of review: a merge, a pull-request reference, a Reviewed-by or Reviewed-on trailer, a Closes/Fixes reference, a maintainer's sign-off on someone else's change, or a change applied by someone other than its author. That is low but not absent. Review may happen in a workflow this history does not record; a buyer should ask how change is approved before it ships.
| 175 of 3,550 commits in the last 24 months carry review evidence; 7.7% across all 17,857 |
Almost no process scaffolding exists in the repository
adequateOf five ordinary markers — CI workflows, CODEOWNERS, a pull-request template, pre-commit hooks, contribution guidance — 1 is present: CI workflows. Branch protection itself is a GitHub setting rather than a file, so this is a reading of proxies and not of the rules themselves. What it does establish is that the process is not written down anywhere a new engineer would find it.
| 1 of 5 markers present across 7,856 tracked files |
Product & Engineering Maturity
adequate18% of bug fixes add or change a test
adequateOf 865 fixes in the last 24 months, 155 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.
| 155 of 865 |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v3.7.6, is not on the branch this survey read; the newest release on it is v3.7.5. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v3.7.6 |
Security & Reliability Posture
adequate1 credential-shaped string in the tree sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key.
| Google API key, where fakes are usual |
None 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 7,856 tracked files; 0 present |
1 locked dependency has published vulnerabilities, 1 high or critical
adequate1 of 139 locked dependencies match 1 published advisories in OSV, 1 of them rated high or critical. 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.
Companion/Gemfile.lock — rubyzip 2.4.1: GHSA-47m2-wp7j-p9vc (high), fixed in 3.4.0 |
12 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.
ThirdParty/BTree — 16 tracked files, no licence file |
ThirdParty/CGSInternal — 17 tracked files, no licence file |
ThirdParty/Highlightr.framework — 98 tracked files, no licence file |
ThirdParty/NMSSH.framework — 19 tracked files, no licence file |
ThirdParty/NSURL-IDN — 2 tracked files, no licence file |
ThirdParty/SFSymbolEnum — 4 tracked files, no licence file |
4 advisories against this project in the last 24 months, 2 high or critical
adequateThe newest was published on 2026-11-05. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 2 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 3.7.5. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 2 records name iTerm2 with nothing tying them to this repository (CVE-2019-9535, CVE-2022-45872).
| 2026-11-05: CVE-2026-123014 (high): iTerm2 before 3.7.7beta2 has an argument injection vulnerability in the x-man-page: URL handler, allowing an attacker to execute arbitrary commands with the pri |
| 2026-10-07: CVE-2026-88514 (moderate): An issue in iTerm2 macOS before 3.6.12 allows a local attacker to obtain sensitive information. |
| 2026-04-18: CVE-2026-41253 (moderate): In iTerm2 through 3.6.9, displaying a .txt file can cause code execution via DCS 2000p and OSC 135 data, if the working directory contains a malicious file whos |
| 2025-01-03: CVE-2025-22275 (critical): iTerm2 3.5.6 through 3.5.10 before 3.5.11 sometimes allows remote attackers to obtain sensitive information from terminal commands by reading the /tmp/framer.tx |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 6,043 readable files references an instrumentation, metrics or error-reporting library. If this system is in production, nobody learns that it broke from the system itself — they learn it from a customer. That is a reliability finding before it is an observability one.
| searched 6,043 tracked text files for 16 known instrumentation libraries; manifests for metrics, tracing and error-reporting families; locked dependencies for the packages that emit; 0 matched |
No structured logging library is in use
adequateNothing references a structured logging library. Logs that are written to be read by a person are not searchable by a machine, which means incident response here is proportional to how well someone remembers the codebase rather than to what the tooling can find.
| C source is not searched: C programs log through printf-style calls unless they take a library, and none of the 10 searched for is referenced |
No error reporter is wired in
adequateNothing in the service initialises an error reporter (Sentry, Rollbar, Bugsnag, Honeybadger or an APM agent). An exception in production reaches a person only if someone is reading the logs, which usually means a customer reports it first.
| no error reporter initialised |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on gnachman/iterm2: 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.