Read 2026-10-23
butterbase-ai/butterbase: technical due diligence, read from its repository
What Borehole read in butterbase-ai/butterbase's code and history at 6faacd7: 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 | strong |
| Fit with the Acquirer | not assessable |
What the repository says
.gitmodules:1: 1 submodule(s) this survey does not read: packages/plugin
Architecture & Codebase — including AI provenance
strongservices/storage-indexer/worker-configuration.d.ts is 13,545 lines, 145× this codebase's median file
adequateThe median source file here is 93 lines. 17 files exceed 1,000 lines, the largest being 13,545. 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.
services/storage-indexer/worker-configuration.d.ts:1 — 13,545 lines (145× median) |
services/control-api/src/services/neon-task-worker.ts:1 — 2,720 lines (29× median) |
db/runtime-plane/001_initial_runtime_schema.sql:1 — 2,440 lines (26× median) |
services/control-api/src/routes/admin.ts:1 — 2,316 lines (24× median) |
services/control-api/src/services/dashboard-agent/loop.ts:1 — 2,229 lines (23× 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: 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,280 tracked files |
Tests are retried until they pass
adequateThe suite is configured to retry failing tests (services/control-api/src/services/spa-routing-probe.test.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.
services/control-api/src/services/spa-routing-probe.test.ts:108 — test retry |
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate5 Dockerfiles run the application as root
adequateNo USER instruction switches away from root, so the process runs with full privileges inside the container. It is a one-line fix and an ordinary expectation, which is why its absence is worth asking about: it usually says more about whether anyone has reviewed the deployment than about this container specifically.
packages/static-frontend-worker/Dockerfile — runs as root |
services/agent-runtime/Dockerfile — runs as root |
services/control-api/Dockerfile — runs as root |
services/deno-runtime/Dockerfile — runs as root |
87 SQL statements built from strings
adequate87 places in product code build SQL by formatting or joining strings rather than passing parameters, and in 20 of them a value, not a table or column name, goes into the string. Where any of those values comes from a request, it is an injection point. Each site needs a look; the fix, parameters, is small.
services/control-api/src/routes/admin.ts:1975 — SQL built from a string |
services/control-api/src/routes/audit-logs.ts:172 — SQL built from a string |
services/control-api/src/routes/audit-logs.ts:174 — SQL built from a string |
63 locked dependencies have published vulnerabilities, 67 high or critical in what ships
adequate63 of 1,604 locked dependencies match 183 published advisories in OSV, 85 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.
services/agent-runtime/uv.lock — anyio 4.13.0: GHSA-82r6-8w77-94w6 (critical), fixed in 4.14.2 |
services/agent-runtime/uv.lock — certifi 2026.4.22: GHSA-6q48-6c7w-9gw2 (critical), fixed in 2026.10.19 |
package-lock.json — tar 6.2.1: GHSA-23hp-3jrh-7fpw (critical), fixed in 7.5.19 |
Observability & Operations
strongNo finding.
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on butterbase-ai/butterbase: 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.