Read 2026-10-04
codeberg.org/mergiraf/mergiraf: technical due diligence, read from its repository
What Borehole read in codeberg.org/mergiraf/mergiraf's code and history at 6feadf4: 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 | strong |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
adequateThe repository begins with most of itself already written
adequateThe first commit carries 26,197 lines — 43% of every line ever added. Whatever happened before that commit happened somewhere this repository cannot show you, so the early history is not available as evidence of how the system was designed.
| 2024-11-01T13:06:12+00:00; +26,197 across 683 files; subject: 'Initial release' |
src/ast.rs is 2,204 lines, 314× this codebase's median file
adequateThe median source file here is 7 lines. 5 files exceed 1,000 lines, the largest being 2,204. 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/ast.rs:1 — 2,204 lines (314× median) |
src/supported_langs.rs:1 — 1,716 lines (245× median) |
src/parsed_merge.rs:1 — 1,357 lines (193× median) |
src/ast/bundle_comments.rs:1 — 1,326 lines (189× median) |
src/tree_builder.rs:1 — 1,116 lines (159× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate14% of bug fixes add or change a test
adequateOf 105 fixes in the last 24 months, 15 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.
| 15 of 105 |
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 1,576 tracked files; 0 present |
The build runs third-party code it does not pin
adequate1 step pipes 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.
.forgejo/workflows/Dockerfile:11 — download piped into a shell |
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 codeberg.org/mergiraf/mergiraf: 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.