Read 2026-11-03
mail-0/zero: technical due diligence, read from its repository
What Borehole read in mail-0/zero's code and history at 3613273: 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 | strong |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
LICENSE: Relicensed: MIT → AGPL-3.0 (2025-03-02) → MIT (2025-03-08)
Architecture & Codebase — including AI provenance
strongapps/server/src/routes/agent/index.ts is 4,017 lines, 60× this codebase's median file
adequateThe median source file here is 66 lines. 13 files exceed 1,000 lines, the largest being 4,017. 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.
apps/server/src/routes/agent/index.ts:1 — 4,017 lines (60× median) |
apps/mail/components/create/email-composer.tsx:1 — 2,072 lines (31× median) |
apps/mail/components/context/command-palette-context.tsx:1 — 1,926 lines (29× median) |
apps/mail/components/icons/icons.tsx:1 — 1,830 lines (27× median) |
apps/mail/components/mail/mail-display.tsx:1 — 1,806 lines (27× median) |
Engineering Process & SDLC Maturity
strongTests are retried until they pass
adequateThe suite is configured to retry failing tests (packages/testing/playwright.config.ts). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.
packages/testing/playwright.config.ts:15 — test retry |
Product & Engineering Maturity
adequate107 direct dependencies in a single manifest
adequateapps/mail/package.json declares 107 direct dependencies. Each one is a maintenance obligation, a supply-chain surface and a potential licence question that transfers with the asset. The count says nothing about whether any given dependency was a good choice; it says how many such choices a buyer inherits.
apps/mail/package.json — 107 declared |
apps/server/package.json — 66 declared |
package.json — 2 declared |
0% of bug fixes add or change a test
adequateOf 606 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 606 |
Security & Reliability Posture
adequate1 Dockerfile runs the application as root
adequateNo USER instruction switches away from root, so the process runs with full privileges inside the container. It is a one-line fix and an ordinary expectation, which is why its absence is worth asking about: it usually says more about whether anyone has reviewed the deployment than about this container specifically.
docker/db/Dockerfile — runs as root |
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/ci.yml:19 — action pinned by tag |
.github/workflows/deploy-to-prod-command.yml:35 — action pinned by tag |
2 SQL statements built from strings
adequate2 places in product code build SQL by formatting or joining strings rather than passing parameters. In each, what the code shows going in is a table or column name, a constant, or something the line does not show, not a request's value. Ask whether any value reaches these strings, rather than a parameter.
apps/server/src/lib/imap/imap-store.ts:382 — SQL built from a string |
apps/server/src/lib/imap/imap-store.ts:879 — SQL built from a string |
71 locked dependencies have published vulnerabilities, 44 high or critical in what ships
adequate71 of 2,178 locked dependencies match 163 published advisories in OSV, 88 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.
pnpm-lock.yaml — happy-dom 12.10.3: GHSA-37j7-fg3j-429f (critical), fixed in 20.0.0; a development dependency |
pnpm-lock.yaml — tar 7.4.3: GHSA-23hp-3jrh-7fpw (critical), fixed in 7.5.19; reached only by the build |
pnpm-lock.yaml — tinypool 0.8.4: GHSA-5gmw-xhrv-c9v3 (critical), fixed in 2.1.1; a development dependency |
4 places insert HTML from a variable without sanitising it
adequate4 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.
apps/mail/components/mail/mail-content.tsx:113 — HTML from a variable |
apps/mail/components/ui/chart.tsx:73 — HTML from a variable |
apps/mail/lib/email-utils.client.tsx:196 — HTML from a variable |
Relicensed: MIT → AGPL-3.0 (2025-03-02) → MIT (2025-03-08)
adequateThe root licence changed 2 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.
1 advisory against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2025-06-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. None of them affects the surveyed version.
| 2025-06-20: GHSA-34gh-g567-hq85 (high), fixed in 0.81: Session Hijacking Via Email |
Observability & Operations
adequateNo structured logging library is in use
adequateNothing references a structured logging library. Logs that are written to be read by a person are not searchable by a machine, which means incident response here is proportional to how well someone remembers the codebase rather than to what the tooling can find.
| searched 686 files for 10 structured logging libraries; 0 matched |
1 of 4 deployed images carry no version, or `latest`
adequate1 images in the deployment configuration are named without a version or as `latest`. A redeploy can change the software without a commit, a rollback has nothing to roll back to, and nobody can say from the repository what is running.
docker-compose.prod.yaml:83 — image without a version |
The code branches on the environment's name at 12 places
adequate12 places outside configuration test whether they are running in production or staging. Staging then does not exercise production's code, and each deploy is the first run of those branches. Differences belong in configuration the code reads, not in the code.
apps/mail/app/(auth)/login/login-client.tsx:36 — branch on the environment name |
apps/mail/app/(auth)/login/login-client.tsx:73 — branch on the environment name |
apps/mail/app/(auth)/login/login-client.tsx:106 — branch on the environment name |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on mail-0/zero: 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.