Read 2026-10-23
oca/web: technical due diligence, read from its repository
What Borehole read in oca/web's code and history at 884c09e: 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 | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongCommit messages are templated rather than written
adequate41% of commit subjects are exact repeats of another subject, and subject length varies by only 51.4 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.
| 120× '[BOT] post-merge updates' |
| 55× '[UPD] README.rst' |
| 32× 'Added translation using Weblate (Italian)' |
web_responsive/static/src/lib/fuse/fuse.basic.js is 1,336 lines, 55× this codebase's median file
adequateThe median source file here is 24 lines. 1 file exceed 1,000 lines, the largest being 1,336. 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.
web_responsive/static/src/lib/fuse/fuse.basic.js:1 — 1,336 lines (55× median) |
Engineering Process & SDLC Maturity
adequateNothing in the history is tagged as a release
adequateAcross 1.1 years of history there is not one tag. There may still be a deployment process, but this repository holds no record of what shipped when — which is the record a buyer needs to reconstruct an incident or a regression after the fact.
| 0 tags across 1,579 commits and 385 days |
Product & Engineering Maturity
adequate8% of bug fixes add or change a test
adequateOf 317 fixes in the last 24 months, 26 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.
| 26 of 317 |
Security & Reliability Posture
strongNo finding.
Observability & Operations
not assessableNot rated: only 5 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 oca/web: 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.