Read 2026-10-04
codeberg.org/superseriousbusiness/gotosocial: technical due diligence, read from its repository
What Borehole read in codeberg.org/superseriousbusiness/gotosocial's code and history at 34ba880: 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
- Releases are cut from another branch than the one surveyed
Architecture & Codebase — including AI provenance
strongtestrig/testmodels.go is 5,342 lines, 49× this codebase's median file
adequateThe median source file here is 109 lines. 11 files exceed 1,090 lines, the largest being 5,342. 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.
testrig/testmodels.go:1 — 5,342 lines (49× median) |
internal/typeutils/internaltofrontend.go:1 — 3,521 lines (32× median) |
internal/typeutils/internaltoas.go:1 — 2,447 lines (22× median) |
internal/cache/db.go:1 — 2,010 lines (18× median) |
internal/processing/workers/fromfediapi.go:1 — 1,785 lines (16× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate89 direct dependencies in a single manifest
adequatego.mod declares 89 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.
go.mod — 89 declared |
web/source/package.json — 28 declared |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v0.22.1, is not on the branch this survey read; the newest release on it is v0.22.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v0.22.1 |
Security & Reliability Posture
adequate5 credential-shaped strings in the tree sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key.
| 5 cited: AWS access key, where fakes are usual |
2 environment files are committed
adequatevendor/github.com/subosito/gotenv/.env, vendor/github.com/subosito/gotenv/.env.invalid are tracked in git. Environment files are where credentials usually live, and committing one usually means nobody decided how secrets reach the running application. Whatever is in it is in the history for good. Check 05.1 says whether it holds anything credential-shaped.
vendor/github.com/subosito/gotenv/.env — committed environment file |
vendor/github.com/subosito/gotenv/.env.invalid — committed environment file |
7 outbound calls can wait forever
adequate7 HTTP calls use a client with no timeout (Python `requests` without `timeout=`, or Go's default client). When a dependency slows down, each one holds a worker until the connection gives up, and enough of them take the service down with the dependency.
internal/httpclient/client.go:56 — outbound call without a timeout |
internal/httpclient/client.go:102 — outbound call without a timeout |
internal/httpclient/client.go:106 — outbound call without a timeout |
46 locked dependencies have published vulnerabilities, 54 high or critical
adequate46 of 1,197 locked dependencies match 98 published advisories in OSV, 54 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.
web/source/yarn.lock — cipher-base 1.0.4: GHSA-cpq7-6gpm-g9rc (critical), fixed in 1.0.5 |
web/source/yarn.lock — minimist 0.0.5: GHSA-xvch-5gv4-984h (critical), fixed in 0.2.4 |
web/source/yarn.lock — pbkdf2 3.1.2: GHSA-h7cp-r72f-jxh6 (critical), fixed in 3.1.3 |
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 2,393 files for 10 structured logging libraries; 0 matched |
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/superseriousbusiness/gotosocial: 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.