Read 2026-11-03
mlogclub/bbs-go: technical due diligence, read from its repository
What Borehole read in mlogclub/bbs-go's code and history at 2cbeb2a: 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
LICENSE: Relicensed: GPL-3.0 → GPL-2.0 (2019-12-26) → GPL-3.0 (2022-12-13)
Architecture & Codebase — including AI provenance
strongweb/app/routes/dashboard.settings.tsx is 2,933 lines, 36× this codebase's median file
adequateThe median source file here is 81 lines. 7 files exceed 1,000 lines, the largest being 2,933. 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.
web/app/routes/dashboard.settings.tsx:1 — 2,933 lines (36× median) |
web/lib/i18n/messages/en-US.ts:1 — 1,896 lines (23× median) |
web/lib/i18n/messages/zh-CN.ts:1 — 1,850 lines (22× median) |
web/components/editor/rich-text-editor.tsx:1 — 1,189 lines (14× median) |
web/components/topic/topic-create-form.tsx:1 — 1,141 lines (14× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate45 test files against 628 source files (7.2%). 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.
| 45 test files / 628 source files |
61% of commit subjects say nothing about the change
adequate1,313 of 2,139 subjects are either under twelve characters or one of the standard placeholders — wip, fix, update. The history is therefore not usable for reconstructing why a decision was taken, which is the main thing an inheriting engineer needs it for. It says nothing about code quality and a great deal about how much context transfers with the asset.
| 1,313/2,139 low-content subjects (61.4%) |
| '修改build脚本' |
| '删掉多余的代码' |
| '调整包结构' |
| '编辑帖子' |
Product & Engineering Maturity
strongNo finding.
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 988 tracked files; 0 present |
1 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.
Dockerfile — runs as root |
1 environment file is committed
adequateweb/.env is 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.
web/.env — committed environment file |
The build runs third-party code it does not pin
adequate7 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day. Tags have been moved to malicious commits in real supply-chain attacks, and a piped script is whatever the server returns that minute. Pinning to a commit is the fix, and it is small.
.github/workflows/docker-image.yml:36 — action pinned by tag |
.github/workflows/docker-image.yml:39 — action pinned by tag |
12 places insert HTML from a variable without sanitising it
adequate12 places set HTML from a value that is neither a literal nor passed through a sanitiser. Where the value can come from a user, that is stored cross-site scripting, and it is the first thing a buyer's security review looks for in a frontend.
web/app/root.tsx:113 — HTML from a variable |
web/app/routes/about.tsx:51 — HTML from a variable |
web/components/common/image-preview.tsx:213 — HTML from a variable |
2 vendored components with no licence
adequateThird-party code is committed into this repository without any statement of the terms it arrived under. Unknown terms are harder to deal with than inconvenient ones: an awkward licence can be complied with, an absent one cannot. Each of these needs its origin established before the code changes hands.
web/.vite/deps/_metadata.json — 1 tracked files, no licence file |
web/.vite/deps/package.json — 1 tracked files, no licence file |
Relicensed: GPL-3.0 → GPL-2.0 (2019-12-26) → GPL-3.0 (2022-12-13)
adequateThe root licence changed 2 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.
1 advisory against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-10-16. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 1 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 4.4.6. Answer lives in: the release you run, set against each fixed version.
| 2026-10-16: CVE-2026-111639 (high): bbs-go through 4.4.6 contains an authentication bypass vulnerability in the /api/login/google_one_tap endpoint that allows remote attackers to log in as other u |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 681 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 681 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 |
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 mlogclub/bbs-go: 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.