Read 2026-11-03
horizontalsystems/unstoppable-wallet-android: technical due diligence, read from its repository
What Borehole read in horizontalsystems/unstoppable-wallet-android's code and history at 4c78b7d: 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
strongwalletkit/src/main/java/io/horizontalsystems/walletkit/modules/multiswap/providers/USwapProvider.kt is 2,521 lines, 35× this codebase's median file
adequateThe median source file here is 72 lines. 4 files exceed 1,000 lines, the largest being 2,521. 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.
walletkit/src/main/java/io/horizontalsystems/walletkit/modules/multiswap/providers/USwapProvider.kt:1 — 2,521 lines (35× median) |
walletkit/src/main/java/io/horizontalsystems/walletkit/modules/transactions/TransactionViewItemFactory.kt:1 — 1,679 lines (23× median) |
walletkit/src/main/java/io/horizontalsystems/walletkit/ui/compose/components/Text.kt:1 — 1,534 lines (21× median) |
walletkit/src/main/java/io/horizontalsystems/walletkit/modules/multiswap/SwapPage.kt:1 — 1,352 lines (18× median) |
Engineering Process & SDLC Maturity
adequateLittle of the recent change carries a trace of review
adequateIn the last 24 months, 233 of 3,090 commits (7.5%) 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.
| 233 of 3,090 commits in the last 24 months carry review evidence; 51.8% across all 12,123 |
Tests cover a thin slice of the codebase
adequate78 test files against 1,643 source files (4.7%). 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.
| 78 test files / 1,643 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 2,310 tracked files |
Product & Engineering Maturity
adequate1% of bug fixes add or change a test
adequateOf 314 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 314 |
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 2,310 tracked files; 0 present |
1 locked dependency has published vulnerabilities
adequate1 of 104 locked dependencies match 5 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.
gradle/libs.versions.toml — org.bouncycastle:bcprov-jdk15on 1.70: GHSA-4h8f-2wvx-gg5w (moderate), fixed in 1.78 |
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 horizontalsystems/unstoppable-wallet-android: 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.