Read 2026-11-03
inkeep/open-knowledge: technical due diligence, read from its repository
What Borehole read in inkeep/open-knowledge's code and history at bbbf3fe: 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 | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongpackages/desktop/src/main/index.ts is 7,228 lines, 61× this codebase's median file
adequateThe median source file here is 118 lines. 52 files exceed 1,180 lines, the largest being 7,228. 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.
packages/desktop/src/main/index.ts:1 — 7,228 lines (61× median) |
packages/server/src/server-factory.ts:1 — 6,286 lines (53× median) |
packages/server/src/api-extension.ts:1 — 6,000 lines (50× median) |
packages/server/src/file-watcher.ts:1 — 5,247 lines (44× median) |
packages/app/src/components/acp/ThreadView.tsx:1 — 4,917 lines (41× median) |
Engineering Process & SDLC Maturity
adequate3 committed .only switches other tests off
adequate3 test files commit a focused `.only`, which runs that test and silently skips the rest of its suite. 237 skip markers across 58 of 4236 test files. Each is a failure somebody chose to stop seeing; the question is whether anyone is tracking them.
packages/desktop/tests/smoke/_helpers/parse-timeouts.test.ts:1074 — committed .only: other tests do not run |
scripts/check-known-reds.uncached.test.mjs:272 — committed .only: other tests do not run |
packages/app/tests/integration/composition-sweep-index.test.ts:4 — skipped test |
packages/app/tests/integration/e2e-stop-rules.test.ts:665 — skipped test |
packages/app/tests/integration/stale-external-write-rollback.test.ts:302 — skipped test |
Tests are retried until they pass
adequateThe suite is configured to retry failing tests (packages/desktop/playwright.config.ts). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.
packages/desktop/playwright.config.ts:29 — test retry |
14% of recent commits change more than 2,000 lines
adequate273 of 1960 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.
| 273 commits over 2,000 lines |
Product & Engineering Maturity
adequate108 direct dependencies in a single manifest
adequatepackages/app/package.json declares 108 direct dependencies. Each one is a maintenance obligation, a supply-chain surface and a potential licence question that transfers with the asset. The count says nothing about whether any given dependency was a good choice; it says how many such choices a buyer inherits.
packages/app/package.json — 108 declared |
packages/core/package.json — 61 declared |
packages/server/package.json — 43 declared |
packages/cli/package.json — 20 declared |
Security & Reliability Posture
adequate33 credential-shaped strings in the tree sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key.
| 5 cited: GitHub token, where fakes are usual |
51 locked dependencies have published vulnerabilities, 38 high or critical in what ships
adequate51 of 2,448 locked dependencies match 140 published advisories in OSV, 72 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.
pnpm-lock.yaml — @simple-git/argv-parser 1.1.1: GHSA-v5rq-49vh-5v5c (critical), fixed in 2.0.1 |
pnpm-lock.yaml — dompurify 3.4.13: GHSA-cg2g-xh64-v4q7 (critical), fixed in 3.4.17 |
pnpm-lock.yaml — proxy-addr 2.0.7: GHSA-jqcg-44mw-7w3h (critical), fixed in 2.0.8 |
12 places insert HTML from a variable without sanitising it
adequate12 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.
packages/app/src/components/EditorActivityPool.tsx:725 — HTML from a variable |
packages/app/src/editor/components/Math.tsx:25 — HTML from a variable |
packages/app/src/editor/components/Mirror.tsx:111 — 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 inkeep/open-knowledge: 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.