Read 2026-11-07
codeberg.org/simonrepp/faircamp: technical due diligence, read from its repository
What Borehole read in codeberg.org/simonrepp/faircamp's code and history at c06ca6e: 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
LICENSE.txt: Relicensed: GPL-3.0 → AGPL-3.0 (2022-12-23)CONTRIBUTING.md:34: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongdesktop/src/persist.rs is 2,067 lines, 18× this codebase's median file
adequateThe median source file here is 109 lines. 5 files exceed 1,090 lines, the largest being 2,067. 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.
desktop/src/persist.rs:1 — 2,067 lines (18× median) |
core/src/site.rs:1 — 1,776 lines (16× median) |
core/src/multitrack.rs:1 — 1,599 lines (14× median) |
core/src/manifest/from_manifest.rs:1 — 1,439 lines (13× median) |
renderer/assets/player.js:1 — 1,351 lines (12× median) |
Engineering Process & SDLC Maturity
adequateChange lands on the trunk with no trace of review
adequateIn the last 24 months, 6 of 657 commits (0.9%) carry any trace of review: a merge, a pull-request reference, a Reviewed-by or Reviewed-on trailer, a Closes/Fixes reference, a maintainer's sign-off on someone else's change, or a change applied by someone other than its author. Every common review workflow leaves at least one of those, so either review happens somewhere this history cannot see, or it is not happening. A buyer should establish which before relying on the review story they are told.
| 6 of 657 commits in the last 24 months carry review evidence; 1.0% across all 1,365 |
Tests are absent or token
adequate0 test files against 338 source files (0.0%). 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.
| 0 test files / 338 source files |
Almost no process scaffolding exists in the repository
adequateOf five ordinary markers — CI workflows, CODEOWNERS, a pull-request template, pre-commit hooks, contribution guidance — 1 is present: contribution guidance. Branch protection itself is a GitHub setting rather than a file, so this is a reading of proxies and not of the rules themselves. What it does establish is that the process is not written down anywhere a new engineer would find it.
| 1 of 5 markers present across 598 tracked files |
Product & Engineering Maturity
not assessableNot rated: only 8 of 19 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
Security & Reliability Posture
adequateNone of the standard security guard rails are configured
adequateThere is no disclosure policy, no automated dependency updates, no named code owners and no pre-commit configuration. None of these is load-bearing on its own. Their collective absence says that security posture here is whatever the current team happens to remember to do, which is not a posture that survives the team changing.
| checked 5 kinds of guard rail across 598 tracked files; 0 present |
30 locked dependencies have published vulnerabilities, 4 high or critical
adequate30 of 896 locked dependencies match 52 published advisories in OSV, 4 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 8.6.0: GHSA-m665-v7pm-7grj (critical), fixed in 9.0.5 |
Cargo.lock — block-buffer 0.12.0: GHSA-qwgh-2vcv-g2f7 (moderate) |
Cargo.lock — grid 1.0.0: GHSA-38c5-483c-4qqp (moderate), fixed in 1.0.1 |
Relicensed: GPL-3.0 → AGPL-3.0 (2022-12-23)
adequateThe root licence changed 1 time(s). The latest terms restrict what users, hosts or a buyer may do in ways the earlier ones did not. Code taken under the old terms stays under them, so both matter in diligence.
LICENSE.txt — GPL-3.0 from 2021-02-08 |
LICENSE.txt — AGPL-3.0 from 2022-12-23 |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 431 readable files references an instrumentation, metrics or error-reporting library. If this system is in production, nobody learns that it broke from the system itself — they learn it from a customer. That is a reliability finding before it is an observability one.
| searched 431 tracked text files for 16 known instrumentation libraries; manifests for metrics, tracing and error-reporting families; locked dependencies for the packages that emit; 0 matched |
One 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 codeberg.org/simonrepp/faircamp: 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.