Read 2026-11-03
flectar/mail: technical due diligence, read from its repository
What Borehole read in flectar/mail's code and history at 240c752: 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 | strong |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongcrates/flectar-mail-core/src/lib.rs is 11,564 lines, 55× this codebase's median file
adequateThe median source file here is 209 lines. 14 files exceed 2,090 lines, the largest being 11,564. 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.
crates/flectar-mail-core/src/lib.rs:1 — 11,564 lines (55× median) |
src/main.rs:1 — 8,598 lines (41× median) |
src/mail.rs:1 — 4,245 lines (20× median) |
crates/flectar-mail-core/src/sync/engine.rs:1 — 4,237 lines (20× median) |
crates/flectar-mail-core/src/sync/gmail.rs:1 — 4,214 lines (20× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate16% of bug fixes add or change a test
adequateOf 216 fixes in the last 24 months, 35 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.
| 35 of 216 |
Security & Reliability Posture
strong7 locked dependencies have published vulnerabilities, 1 high or critical
adequate7 of 1,093 locked dependencies match 7 published advisories in OSV, 1 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.
Cargo.lock — zip 9.0.4: GHSA-m665-v7pm-7grj (critical), fixed in 9.0.5 |
Cargo.lock — bincode 2.0.1: RUSTSEC-2025-0141 (unrated) |
Cargo.lock — paste 1.0.15: RUSTSEC-2024-0436 (unrated) |
Observability & Operations
not assessableNot rated: only 4 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 flectar/mail: 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.