Read 2026-10-23
bloomberg/blazingmq: technical due diligence, read from its repository
What Borehole read in bloomberg/blazingmq's code and history at 62b75f8: 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 | adequate |
| Engineering Process & SDLC Maturity | adequate |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
adequatesrc/groups/bmq/bmqimp/bmqimp_brokersession.t.cpp is 9,844 lines, 41× this codebase's median file
adequateThe median source file here is 236 lines. 25 files exceed 2,360 lines, the largest being 9,844. 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.
src/groups/bmq/bmqimp/bmqimp_brokersession.t.cpp:1 — 9,844 lines (41× median) |
src/groups/mqb/mqbs/mqbs_filestore.cpp:1 — 7,953 lines (33× median) |
src/groups/bmq/bmqimp/bmqimp_brokersession.cpp:1 — 7,541 lines (31× median) |
src/groups/mqb/mqbblp/mqbblp_clusterqueuehelper.cpp:1 — 6,271 lines (26× median) |
src/groups/bmq/bmqp/bmqp_protocol.h:1 — 5,260 lines (22× median) |
1 base image floats: no version, or `latest`
adequate1 of 4 `FROM` lines in product Dockerfiles name an image without a version, or with `latest`. Each build pulls whatever the registry serves that day, so the image that ships can change without a commit, and last month's build cannot be reproduced. Pin a version, or a digest.
docker/plugins/bmqprometheus/Dockerfile:1 — base image without a version |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate60 test files against 1,209 source files (5.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.
| 60 test files / 1,209 source files |
Tests are retried until they pass
adequateThe suite is configured to retry failing tests (.github/workflows/manual.yaml). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.
.github/workflows/manual.yaml:139 — test retry |
Product & Engineering Maturity
adequateEffort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.17 to 0.86 between the first and second halves of this history. Rework is normal and often healthy, but a rising ratio means an increasing share of the team's time is spent replacing code that already exists rather than building what does not. Whether that is deliberate repayment or churn is a question for the team.
| first half 0.17, second half 0.86 (split 2025-02-21) |
13% of bug fixes add or change a test
adequateOf 558 fixes in the last 24 months, 73 touched a test. A fix without the test that would have caught the bug can quietly come back, and the suite never learns from what went wrong.
| 73 of 558 |
Security & Reliability Posture
adequate2 Dockerfiles run 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.
docker/plugins/bmqprometheus/Dockerfile — runs as root |
docker/sanitizers/Dockerfile — runs as root |
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.
| C++ source is not searched: C++ programs log through printf-style calls unless they take a library, and none of the 10 searched for is referenced |
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 |
2 of 3 deployed images carry no version, or `latest`
adequate2 images in the deployment configuration are named without a version or as `latest`. A redeploy can change the software without a commit, a rollback has nothing to roll back to, and nobody can say from the repository what is running.
docker/single-node/docker-compose.yaml:14 — image without a version |
docker/plugins/bmqprometheus/docker-compose.yml:13 — image without a version |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on bloomberg/blazingmq: 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.