Read 2026-11-07
gitlab.com/calcprogrammer1/openrgb: technical due diligence, read from its repository
What Borehole read in gitlab.com/calcprogrammer1/openrgb's code and history at 817834c: 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 | adequate |
| Security & Reliability Posture | strong |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
CONTRIBUTING.md:75: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongdependencies/json/nlohmann/json.hpp is 24,766 lines, 245× this codebase's median file
adequateThe median source file here is 101 lines. 57 files exceed 1,010 lines, the largest being 24,766. 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.
dependencies/json/nlohmann/json.hpp:1 — 24,766 lines (245× median) |
Controllers/RazerController/RazerDevices.cpp:1 — 10,063 lines (99× median) |
dependencies/httplib/httplib.h:1 — 9,807 lines (97× median) |
Controllers/GigabyteRGBFusion2USBController/GigabyteFusion2USB_Devices.cpp:1 — 7,854 lines (77× median) |
Controllers/LogitechController/LogitechHIDPP20Controller/LogitechHIDPP20Controller.cpp:1 — 7,639 lines (75× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate34 test files against 2,095 source files (1.6%). 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.
| 34 test files / 2,095 source files |
Product & Engineering Maturity
adequate0% of bug fixes add or change a test
adequateOf 328 fixes in the last 24 months, 0 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.
| 0 of 328 |
Security & Reliability Posture
strongNo finding.
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 2,167 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 2,167 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 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 |
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 gitlab.com/calcprogrammer1/openrgb: 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.