Read 2026-11-03
vectifyai/openkb: technical due diligence, read from its repository
What Borehole read in vectifyai/openkb's code and history at ff54396: 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 | strong |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
Architecture & Codebase — including AI provenance
strongopenkb/cli.py is 3,809 lines, 29× this codebase's median file
adequateThe median source file here is 128 lines. 3 files exceed 1,280 lines, the largest being 3,809. 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.
openkb/cli.py:1 — 3,809 lines (29× median) |
openkb/agent/compiler.py:1 — 2,373 lines (18× median) |
frontend/src/pages/KbDetail.tsx:1 — 1,291 lines (10× median) |
Engineering Process & SDLC Maturity
strongAlmost 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: CI workflows. 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 293 tracked files |
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, v0.4.5, is not on the branch this survey read; the newest release on it is v0.4.4. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v0.4.5 |
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 293 tracked files; 0 present |
23 locked dependencies have published vulnerabilities, 55 high or critical in what ships
adequate23 of 372 locked dependencies match 121 published advisories in OSV, 55 of them rated high or critical. A lockfile says which version is installed, not whether the flawed code is reachable from this product, so each needs a look. Most are fixed by an upgrade, and the advisory names the version.
5 places insert HTML from a variable without sanitising it
adequate5 places set HTML from a value that is neither a literal nor passed through a sanitiser. Where the value can come from a user, that is stored cross-site scripting, and it is the first thing a buyer's security review looks for in a frontend.
frontend/src/components/MarkdownView.tsx:81 — HTML from a variable |
frontend/src/components/MarkdownView.tsx:172 — HTML from a variable |
frontend/src/components/MarkdownView.tsx:200 — HTML from a variable |
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 vectifyai/openkb: 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.