Read 2026-11-03
btraceio/btrace: technical due diligence, read from its repository
What Borehole read in btraceio/btrace's code and history at a2bc8e6: 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 | adequate |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
- No release for 24 months while development continues
- Releases are cut from another branch than the one surveyed
LICENSE.txt: Relicensed: GPL-with-exception → Apache-2.0 (2026-05-03)
Architecture & Codebase — including AI provenance
strongbtrace-core/src/main/java/io/btrace/core/BTraceUtils.java is 6,311 lines, 100× this codebase's median file
adequateThe median source file here is 63 lines. 12 files exceed 1,000 lines, the largest being 6,311. 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.
btrace-core/src/main/java/io/btrace/core/BTraceUtils.java:1 — 6,311 lines (100× median) |
btrace-agent/src/main/java24/io/btrace/instr/ClassFileApiBackend.java:1 — 3,771 lines (59× median) |
btrace-agent/src/main/java/io/btrace/instr/Instrumentor.java:1 — 1,955 lines (31× median) |
btrace-agent/src/main/java/io/btrace/instr/InstrumentingMethodVisitor.java:1 — 1,934 lines (30× median) |
btrace-agent/src/main/java/io/btrace/instr/Preprocessor.java:1 — 1,857 lines (29× median) |
Engineering Process & SDLC Maturity
adequate7% of recent commits change more than 2,000 lines
adequate26 of 363 commits in the last 24 months changed over 2,000 lines of code, not counting reformatting, renames, vendored or generated code. A change that size is rarely reviewed line by line. Ask how they were reviewed, and what made them that large.
| 26 commits over 2,000 lines |
Product & Engineering Maturity
adequateNo release for 24 months while development continues
adequateThe last tag, v2.2.6, was cut 723 days before the survey; the typical gap between releases was 122 days, and 129 commits landed in the last 90 days. Users run the last release, not this code.
| last tag v2.2.6 |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v2.2.6, is not on the branch this survey read; the newest release on it is v2.2.2. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v2.2.6 |
Security & Reliability Posture
adequate1 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.
docker/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate3 steps pipe a download straight into a shell. 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/continuous.yml:147 — download piped into a shell |
4 deserialisers that can run code
adequate4 places read data with a deserialiser that executes what it reads (Java object streams). That is safe on data the system wrote itself and remote code execution on anything else. Ask where each one's input comes from.
btrace-core/src/jmh/java/io/btrace/core/comm/v2/BinaryProtocolBenchmark.java:191 — code-executing deserialiser |
btrace-core/src/jmh/java/io/btrace/core/comm/v2/BinaryProtocolBenchmark.java:220 — code-executing deserialiser |
btrace-core/src/main/java/io/btrace/core/comm/JavaSerializationProtocol.java:69 — code-executing deserialiser |
Relicensed: GPL-with-exception → Apache-2.0 (2026-05-03)
adequateThe root licence changed 1 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.
LICENSE.txt — GPL-with-exception from 2008-03-06 |
LICENSE — Apache-2.0 from 2026-05-03 |
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 1,257 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 btraceio/btrace: 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.