Read 2026-11-03
monica-pass/monica: technical due diligence, read from its repository
What Borehole read in monica-pass/monica's code and history at 2ef9f3d: 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 | not assessable |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongMonica for Android/mdbx-engine/src/main/java/uniffi/mdbx_ffi/mdbx_ffi.kt is 19,134 lines, 191× this codebase's median file
adequateThe median source file here is 100 lines. 82 files exceed 1,000 lines, the largest being 19,134. 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.
Monica for Android/mdbx-engine/src/main/java/uniffi/mdbx_ffi/mdbx_ffi.kt:1 — 19,134 lines (191× median) |
Monica for Android/app/src/main/java/takagi/ru/monica/utils/KeePassKdbxService.kt:1 — 10,086 lines (100× median) |
Monica for Android/app/src/main/java/takagi/ru/monica/repository/MdbxVaultStore.kt:1 — 6,838 lines (68× median) |
Monica for Android/app/src/main/java/takagi/ru/monica/ui/screens/AddEditPasswordScreen.kt:1 — 6,488 lines (64× median) |
Monica for Android/app/src/main/java/takagi/ru/monica/utils/WebDavHelper.kt:1 — 6,447 lines (64× median) |
Engineering Process & SDLC Maturity
adequateLittle of the recent change carries a trace of review
adequateIn the last 24 months, 125 of 1,283 commits (9.7%) 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.
| 125 of 1,283 commits in the last 24 months carry review evidence; 9.7% across all 1,283 |
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 5,522 tracked files |
18% of recent commits change more than 2,000 lines
adequate163 of 900 commits in the last 24 months changed over 2,000 lines of code, not counting reformatting, renames, vendored or generated code. A change that size is rarely reviewed line by line. Ask how they were reviewed, and what made them that large.
| 163 commits over 2,000 lines |
Product & Engineering Maturity
not assessableNot rated: only 8 of 19 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
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 5,522 tracked files; 0 present |
The build runs third-party code it does not pin
adequate4 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day. Tags have been moved to malicious commits in real supply-chain attacks, and a piped script is whatever the server returns that minute. Pinning to a commit is the fix, and it is small.
.github/workflows/Android-Preview.yml:351 — action pinned by tag |
.github/workflows/Android.yml:30 — action pinned by tag |
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.
Monica for Android/app/src/main/AndroidManifest.xml:87 — 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 monica-pass/monica: 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.