Read 2026-10-04
genymobile/scrcpy: technical due diligence, read from its repository
What Borehole read in genymobile/scrcpy's code and history at 19c1261: 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 | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongapp/src/cli.c is 3,592 lines, 49× this codebase's median file
adequateThe median source file here is 73 lines. 5 files exceed 1,000 lines, the largest being 3,592. 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.
app/src/cli.c:1 — 3,592 lines (49× median) |
app/src/screen.c:1 — 1,330 lines (18× median) |
app/src/server.c:1 — 1,225 lines (16× median) |
app/src/input_manager.c:1 — 1,213 lines (16× median) |
app/src/scrcpy.c:1 — 1,037 lines (14× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate21 test files against 302 source files (7.0%). This does not measure whether the tests are good, only whether enough of them exist for the codebase to be changed safely by someone who did not write it — which is exactly the situation after an acquisition.
| 21 test files / 302 source files |
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 371 tracked files |
Product & Engineering Maturity
adequate1% of bug fixes add or change a test
adequateOf 87 fixes in the last 24 months, 1 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.
| 1 of 87 |
Security & Reliability Posture
adequateNone 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 371 tracked files; 0 present |
9 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.
app/deps/README — 1 tracked files, no licence file |
app/deps/_init — 1 tracked files, no licence file |
app/deps/adb_linux.sh — 1 tracked files, no licence file |
app/deps/adb_macos.sh — 1 tracked files, no licence file |
app/deps/adb_windows.sh — 1 tracked files, no licence file |
app/deps/dav1d.sh — 1 tracked files, no licence file |
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 genymobile/scrcpy: 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.