Read 2026-10-04
lemmynet/lemmy: technical due diligence, read from its repository
What Borehole read in lemmynet/lemmy's code and history at 8d83bcf: 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 | strong |
| 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
.gitmodules:1: 1 submodule(s) this survey does not read: crates/email/translations
Architecture & Codebase — including AI provenance
strongcrates/db_views/post/src/test.rs is 2,440 lines, 73× this codebase's median file
adequateThe median source file here is 33 lines. 10 files exceed 1,000 lines, the largest being 2,440. 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/db_views/post/src/test.rs:1 — 2,440 lines (73× median) |
crates/db_views/report_combined/src/impls.rs:1 — 1,335 lines (40× median) |
migrations/2020-06-30-135809_remove_mat_views/up.sql:1 — 1,265 lines (38× median) |
crates/api/api_utils/src/utils.rs:1 — 1,160 lines (35× median) |
crates/db_views/comment/src/impls.rs:1 — 1,148 lines (34× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate108 test files against 1,234 source files (8.8%). 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.
| 108 test files / 1,234 source files |
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, 0.19.20, is not on the branch this survey read; the newest release on it is 0.19.5. The shipped product may differ from what this report describes. Survey the release branch too.
| tag 0.19.20 |
Security & Reliability Posture
adequate30 locked dependencies have published vulnerabilities, 7 high or critical
adequate30 of 833 locked dependencies match 61 published advisories in OSV, 7 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. None of the high or critical ones is in what the product ships: 1 apply only under a condition the advisory states, which a lockfile cannot settle. 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 — lettre 0.11.19: GHSA-4pj9-g833-qx53 (critical), fixed in 0.11.22 |
Cargo.lock — wasmtime 37.0.3: GHSA-jhxm-h53p-jm7w (critical), fixed in 36.0.7; the advisory applies only under a condition it states |
Cargo.lock — diesel 2.3.7: GHSA-h5x4-m2qf-r4f2 (high), fixed in 2.3.8 |
22 advisories against this project in the last 24 months
adequateThe newest was published on 2026-06-09. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. GHSA-2hrg-7x4g-9vpg (moderate) is fixed in the surveyed commit; which release carries it cannot be told from this history, which does not place the release users run. Answer lives in: the version you run.
| 2026-06-09: GHSA-2hrg-7x4g-9vpg (moderate): Rate limit bypass via X-Forwarded-For header spoofing in actix-web ConnectionInfo |
| 2026-06-09: GHSA-2g66-9fr3-ppwj (low): Stored XSS via markdown image alt-text in lemmy-ui html5-embed |
| 2026-06-09: GHSA-xgg7-8hvq-8m65 (moderate): Login Endpoint User Enumeration via HTTP Response Code Differential |
| 2026-06-09: GHSA-gwfj-h8r7-792v (low): `CollectionAdd::Featured` does not check the post is in the community |
| 2026-06-09: GHSA-46g9-847m-qf8r (low): Blocked users can edit private messages sent before the block |
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 |
No error reporter is wired in
adequateNothing in the service initialises an error reporter (Sentry, Rollbar, Bugsnag, Honeybadger or an APM agent). An exception in production reaches a person only if someone is reading the logs, which usually means a customer reports it first.
| no error reporter initialised |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on lemmynet/lemmy: 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.