Read 2026-10-04
monicahq/monica: technical due diligence, read from its repository
What Borehole read in monicahq/monica's code and history at 6e6ec21: 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 | strong |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
Architecture & Codebase — including AI provenance
adequateThe repository begins with most of itself already written
adequateThe first commit carries 276,373 lines — 42% 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.
| 2021-12-04T23:26:14+00:00; +276,373 across 415 files; subject: 'chore: first commit' |
app/Domains/Settings/CreateAccount/Jobs/SetupAccount.php is 1,218 lines, 17× this codebase's median file
adequateThe median source file here is 68 lines. 1 file exceed 1,000 lines, the largest being 1,218. 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/Domains/Settings/CreateAccount/Jobs/SetupAccount.php:1 — 1,218 lines (17× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate8% of bug fixes add or change a test
adequateOf 39 fixes in the last 24 months, 3 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.
| 3 of 39 |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v4.1.2, is not on the branch this survey read; the newest pre-release on it is v5.0.0-beta.5. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v4.1.2 |
Security & Reliability Posture
adequate1 environment file is committed
adequate.env.example.sail is tracked in git. Environment files are where credentials usually live, and committing one usually means nobody decided how secrets reach the running application. Whatever is in it is in the history for good. Check 05.1 says whether it holds anything credential-shaped.
.env.example.sail — committed environment file |
The build runs third-party code it does not pin
adequate16 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/deploy.yml:17 — action pinned by tag |
.github/workflows/docker.yml:52 — action pinned by tag |
47 locked dependencies have published vulnerabilities, 15 high or critical in what ships
adequate47 of 705 locked dependencies match 166 published advisories in OSV, 78 of them rated high or critical. 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.
yarn.lock — tar 7.4.3: GHSA-23hp-3jrh-7fpw (critical), fixed in 7.5.19 |
composer.lock — laravel/framework 12.22.1: GHSA-5vg9-5847-vvmq (high), fixed in 12.60.0 |
composer.lock — league/commonmark 2.7.1: GHSA-2q4p-g7hv-5rgv (high), fixed in 2.9.0 |
18 places insert HTML from a variable without sanitising it
adequate18 places set HTML from a value that is neither a literal nor passed through a sanitiser. Where the value can come from a user, that is stored cross-site scripting, and it is the first thing a buyer's security review looks for in a frontend.
resources/js/Components/Pagination.vue:30 — HTML from a variable |
resources/js/Components/Pagination.vue:37 — HTML from a variable |
resources/js/Components/Pagination.vue:53 — HTML from a variable |
2 advisories against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-02-20. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 2 of them are fixed in the code you ship could not be told from this history. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 3 records name monica with nothing tying them to this repository (CVE-2024-45989, CVE-2024-48140, CVE-2024-48142).
| 2026-02-20: CVE-2026-26747 (critical): A Host Header Poisoning vulnerability exists in Monica 4.1.2 due to improper handling of the HTTP Host header in app/Providers/AppServiceProvider.php, combined |
| 2025-02-13: CVE-2024-54951 (moderate): Monica 4.1.2 is vulnerable to Cross Site Scripting (XSS). A malicious user can create a malformed contact and use that contact in the "HOW YOU MET" customizatio |
Observability & Operations
adequateOne request cannot be followed through the logs
adequateNothing in the service carries a request or correlation id, and there is no tracing. When a customer reports a failure, the log lines that belong to their request cannot be picked out from everyone else's.
| no request id, correlation id or tracing found |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on monicahq/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.