Read 2026-10-04
termux/termux-app: technical due diligence, read from its repository
What Borehole read in termux/termux-app's code and history at 8629e63: 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 |
What the repository says
- No release for 16 months while development continues
- Releases are cut from another branch than the one surveyed
Architecture & Codebase — including AI provenance
strongterminal-emulator/src/main/java/com/termux/terminal/TerminalEmulator.java is 3,570 lines, 30× this codebase's median file
adequateThe median source file here is 118 lines. 4 files exceed 1,180 lines, the largest being 3,570. 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.
terminal-emulator/src/main/java/com/termux/terminal/TerminalEmulator.java:1 — 3,570 lines (30× median) |
termux-shared/src/main/java/com/termux/shared/file/FileUtils.java:1 — 2,045 lines (17× median) |
terminal-view/src/main/java/com/termux/view/TerminalView.java:1 — 1,521 lines (12× median) |
termux-shared/src/main/java/com/termux/shared/termux/TermuxConstants.java:1 — 1,339 lines (11× median) |
Engineering Process & SDLC Maturity
strongAlmost 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 346 tracked files |
Product & Engineering Maturity
adequate6% of bug fixes add or change a test
adequateOf 31 fixes in the last 24 months, 2 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.
| 2 of 31 |
No release for 16 months while development continues
adequateThe last tag, v0.119.0-beta.3, was cut 499 days before the survey; the typical gap between releases was 22 days, and 18 commits landed in the last 90 days. Users run the last release, not this code.
| last tag v0.119.0-beta.3 |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v0.118.3, is not on the branch this survey read; the newest release on it is v0.117. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v0.118.3 |
Security & Reliability Posture
adequate1 deserialiser that can run code
adequate1 places read data with a deserialiser that executes what it reads (Java object streams). That is safe on data the system wrote itself and remote code execution on anything else. Ask where each one's input comes from.
termux-shared/src/main/java/com/termux/shared/file/FileUtils.java:1636 — code-executing deserialiser |
Licence text does not match a standard licence
adequateLICENSE.md 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.md:1 — 6 lines, unrecognised |
Observability & Operations
not assessableNot rated: only 5 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 termux/termux-app: 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.