Read 2026-11-07
gitlab.com/famedly/conduit: technical due diligence, read from its repository
What Borehole read in gitlab.com/famedly/conduit's code and history at c201feb: 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 | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
LICENSE: Relicensed: AGPL-3.0 → Apache-2.0 (2020-10-18)
Architecture & Codebase — including AI provenance
strongconduit/src/api/server_server.rs is 2,451 lines, 26× this codebase's median file
adequateThe median source file here is 94 lines. 9 files exceed 1,000 lines, the largest being 2,451. 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.
conduit/src/api/server_server.rs:1 — 2,451 lines (26× median) |
conduit/src/service/admin/mod.rs:1 — 2,242 lines (23× median) |
conduit/src/service/rooms/event_handler/mod.rs:1 — 2,132 lines (22× median) |
conduit/src/api/client_server/sync.rs:1 — 1,883 lines (20× median) |
conduit/src/database/key_value/media.rs:1 — 1,780 lines (18× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate6 test files against 170 source files (3.5%). 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.
| 6 test files / 170 source files |
Product & Engineering Maturity
not assessableReleases are cut from another branch than the one surveyed
adequateThe newest release, v0.10.15, is not on the branch this survey read; the newest release on it is v0.10.4. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v0.10.15 |
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.
complement/Dockerfile — runs as root |
25 locked dependencies have published vulnerabilities, 8 high or critical
adequate25 of 472 locked dependencies match 44 published advisories in OSV, 8 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 — aws-lc-sys 0.29.0: GHSA-65p9-r9h6-22vj (high), fixed in 0.38.0 |
Cargo.lock — hickory-proto 0.25.2: GHSA-3v94-mw7p-v465 (high) |
Cargo.lock — hickory-resolver 0.25.2: GHSA-5j98-2g5x-46v6 (high), fixed in 0.26.2 |
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 gitlab.com/famedly/conduit: 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.