Read 2026-10-04
rfgplk/micron.cpp: technical due diligence, read from its repository
What Borehole read in rfgplk/micron.cpp's code and history at 359349a: 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 | not assessable |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongCommit messages are templated rather than written
adequate34% of commit subjects are exact repeats of another subject, and subject length varies by only 22.9 characters. A log written by someone explaining their reasoning to a future reader does not look like this. The log is therefore weak evidence of intent, whatever the code is like.
| 26× 'changes' |
| 13× 'readme' |
| 7× 'Update README.md' |
src/gfx/vk/__bits/__vk_types.hpp is 4,814 lines, 24× this codebase's median file
adequateThe median source file here is 196 lines. 18 files exceed 1,960 lines, the largest being 4,814. 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/gfx/vk/__bits/__vk_types.hpp:1 — 4,814 lines (24× median) |
src/string/format.hpp:1 — 4,506 lines (22× median) |
src/simd/__bits/__neon_arm64.hpp:1 — 3,981 lines (20× median) |
src/simd/__bits/__neon_arm32.hpp:1 — 3,822 lines (19× median) |
src/simd/aliases/neon.hpp:1 — 2,848 lines (14× median) |
Engineering Process & SDLC Maturity
adequateLittle of the recent change carries a trace of review
adequateIn the last 24 months, 23 of 407 commits (5.7%) carry any trace of review: a merge, a pull-request reference, a Reviewed-by or Reviewed-on trailer, a Closes/Fixes reference, a maintainer's sign-off on someone else's change, or a change applied by someone other than its author. That is low but not absent. Review may happen in a workflow this history does not record; a buyer should ask how change is approved before it ships.
| 23 of 407 commits in the last 24 months carry review evidence; 5.7% across all 407 |
33% of commit subjects say nothing about the change
adequate128 of 393 subjects are either under twelve characters or one of the standard placeholders — wip, fix, update. The history is therefore not usable for reconstructing why a decision was taken, which is the main thing an inheriting engineer needs it for. It says nothing about code quality and a great deal about how much context transfers with the asset.
| 128/393 low-content subjects (32.6%) |
| 'License' |
| '.' |
| '+' |
| '+' |
Almost no process scaffolding exists in the repository
adequateOf five ordinary markers — CI workflows, CODEOWNERS, a pull-request template, pre-commit hooks, contribution guidance — 1 is present: contribution guidance. Branch protection itself is a GitHub setting rather than a file, so this is a reading of proxies and not of the rules themselves. What it does establish is that the process is not written down anywhere a new engineer would find it.
| 1 of 5 markers present across 2,277 tracked files |
24% of recent commits change more than 2,000 lines
adequate88 of 368 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.
| 88 commits over 2,000 lines |
Product & Engineering Maturity
not assessableNot rated: only 8 of 19 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
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 2,277 tracked files; 0 present |
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 rfgplk/micron.cpp: 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.