Read 2026-10-04
radareorg/radare2: technical due diligence, read from its repository
What Borehole read in radareorg/radare2's code and history at e930b1b: 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 | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
stronglibr/arch/p/xtensa/gnu/xtensa-modules.c is 21,471 lines, 226× this codebase's median file
adequateThe median source file here is 95 lines. 233 files exceed 1,000 lines, the largest being 21,471. 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.
libr/arch/p/xtensa/gnu/xtensa-modules.c:1 — 21,471 lines (226× median) |
libr/core/cmd_anal.inc.c:1 — 17,379 lines (182× median) |
libr/arch/p/xtensa/gnu/elf32-xtensa.c:1 — 11,398 lines (119× median) |
libr/core/cmd_print.inc.c:1 — 9,871 lines (103× median) |
libr/core/disasm.c:1 — 8,899 lines (93× median) |
Engineering Process & SDLC Maturity
adequateTests cover a thin slice of the codebase
adequate232 test files against 2,866 source files (8.1%). 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.
| 232 test files / 2,866 source files |
CI runs tests that cannot fail the build
adequate1 test command in CI ends in `|| true` or an equivalent, so the pipeline passes whatever the tests say. A green build then means the tests ran, not that they passed.
.github/workflows/ci.yml:170 — a test command that cannot fail |
Product & Engineering Maturity
strongEffort is shifting from building to rewriting
adequateDeleted lines per line added rose from 0.57 to 0.77 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.57, second half 0.77 (split 2017-12-04) |
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.
sys/filc/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate4 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/build.yml:287 — action pinned by tag |
.github/workflows/build.yml:489 — action pinned by tag |
2 shell commands built from strings
adequate2 places run a command through a shell (`shell=True`, `os.system`, `exec` with a template) rather than passing arguments. Where any part comes from outside, it is command injection. Ask where each one's input comes from.
sys/meson.py:301 — command run through a shell |
sys/meson.py:305 — command run through a shell |
49 advisories against this project in the last 24 months, 12 high or critical
adequateThe newest was published on 2026-09-03. 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 16 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 6.2.2. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 52 records name radare2 with nothing tying them to this repository (CVE-2017-10929, CVE-2017-15368, CVE-2017-15385, …).
| 2026-09-03: GHSA-px7c-gwvj-73vf (high), fixed in 6.2.2: Remote code execution when loading Pebble/SMD binary |
| 2026-08-14: GHSA-fg6f-rj8g-25pq (moderate), fixed in 6.2.0: Uncontrolled resource consumption in radare2 PEF loader |
| 2026-08-14: GHSA-96m5-hvwp-674c (low): Out-of-bounds Read at the end of string in the LUA 5.3 bytecode |
| 2026-08-14: GHSA-r5cr-f9p6-5pvj (low), fixed in 6.1.9: Missing string termination causes heap out-of-bounds read in radare2 bplist parser |
| 2026-08-14: GHSA-c2g2-2mc7-3x5w (low), fixed in 6.1.9: Heap out-of-bounds read in radare2 Mach-O LC_DATA_IN_CODE parser |
Observability & Operations
not assessableNot rated: only 4 of 16 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on radareorg/radare2: 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.