Read 2026-11-03
matsuridayo/nekoboxforandroid: technical due diligence, read from its repository
What Borehole read in matsuridayo/nekoboxforandroid's code and history at 5768494: 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 | adequate |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
adequateThe repository begins with most of itself already written
adequateThe first commit carries 46,925 lines — 71% of every line ever added. Whatever happened before that commit happened somewhere this repository cannot show you, so the early history is not available as evidence of how the system was designed.
| 2023-03-15T00:00:00+00:00; +46,925 across 513 files; subject: 'upload code' |
app/src/main/java/moe/matsuri/nb4a/SingBoxOptions.java is 4,645 lines, 65× this codebase's median file
adequateThe median source file here is 71 lines. 2 files exceed 1,000 lines, the largest being 4,645. 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/main/java/moe/matsuri/nb4a/SingBoxOptions.java:1 — 4,645 lines (65× median) |
app/src/main/java/io/nekohasekai/sagernet/ui/ConfigurationFragment.kt:1 — 1,743 lines (24× median) |
34 errors caught and discarded in product code
adequate34 places catch an error and do nothing with it, across 17 files (0.9 per thousand lines). Each is a failure the system will not report. They surface later as problems nobody can explain, and they are cheap to fix now.
app/src/main/java/io/nekohasekai/sagernet/bg/BaseService.kt:127 — error caught and discarded |
app/src/main/java/io/nekohasekai/sagernet/bg/BaseService.kt:128 — error caught and discarded |
app/src/main/java/io/nekohasekai/sagernet/bg/GuardedProcessPool.kt:36 — error caught and discarded |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate1 test files against 245 source files (0.4%). 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.
| 1 test files / 245 source files |
34% of commit subjects say nothing about the change
adequate131 of 384 subjects are either under twelve characters or one of the standard placeholders — wip, fix, update. The history is therefore not usable for reconstructing why a decision was taken, which is the main thing an inheriting engineer needs it for. It says nothing about code quality and a great deal about how much context transfers with the asset.
| 131/384 low-content subjects (34.1%) |
| 'upload code' |
| 'cleanup' |
| 'update data' |
| 'fix' |
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 538 tracked files |
Product & Engineering Maturity
adequateEffort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.11 to 1.98 between the first and second halves of this history. Rework is normal and often healthy, but a rising ratio means an increasing share of the team's time is spent replacing code that already exists rather than building what does not. Whether that is deliberate repayment or churn is a question for the team.
| first half 0.11, second half 1.98 (split 2024-08-27) |
0% of bug fixes add or change a test
adequateOf 36 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 36 |
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 538 tracked files; 0 present |
1 locked dependency has published vulnerabilities
adequate1 of 70 locked dependencies match 1 published advisories in OSV. 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.
libcore/go.mod — github.com/go-chi/chi/v5 v5.2.2: GHSA-j6qf-3m9c-vwj3 (moderate), fixed in 5.4.0 |
The app allows plain HTTP to any server
adequateThe app's manifest allows unencrypted HTTP app-wide (NSAllowsArbitraryLoads, or cleartext traffic permitted), rather than for named domains. Anything sent over plain HTTP can be read on the network, and enterprise security reviews ask about it. Some apps need it by nature (a podcast or feed reader fetches whatever URL a feed gives), so ask which case this is.
app/src/main/res/xml/network_security_config.xml:3 — cleartext allowed app-wide |
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 matsuridayo/nekoboxforandroid: 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.