Read 2026-11-03
enterpilot/gomodel: technical due diligence, read from its repository
What Borehole read in enterpilot/gomodel's code and history at 471516f: 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 | strong |
| Security & Reliability Posture | adequate |
| Observability & Operations | strong |
| Fit with the Acquirer | not assessable |
What the repository says
.github/pull_request_template.md:5: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongweb/dashboard/src/pages/audit-logs/conversation-helpers.js is 1,545 lines, 10× this codebase's median file
adequateThe median source file here is 143 lines. 3 files exceed 1,430 lines, the largest being 1,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.
web/dashboard/src/pages/audit-logs/conversation-helpers.js:1 — 1,545 lines (10× median) |
internal/usage/reader_mongodb.go:1 — 1,530 lines (10× median) |
internal/providers/gemini/native.go:1 — 1,461 lines (10× median) |
Engineering Process & SDLC Maturity
adequateTests are retried until they pass
adequateThe suite is configured to retry failing tests (web/dashboard/tests/workflows.test.js). 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.
web/dashboard/tests/workflows.test.js:1832 — test retry |
12% of recent commits change more than 2,000 lines
adequate130 of 1044 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.
| 130 commits over 2,000 lines |
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
adequate1 Dockerfile runs 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.
.oss-scanner/Dockerfile — runs as root |
7 SQL statements built from strings
adequate7 places in product code build SQL by formatting or joining strings rather than passing parameters. 4 of them put a value into the string; in the rest, what the code shows going in is a table or column name, a constant, or something the line does not show. Ask whether any value reaches these strings, rather than a parameter.
internal/auditlog/reader_sql.go:162 — SQL built from a string |
internal/conversationstore/store_sql_json.go:84 — SQL built from a string |
internal/usage/reader_sql.go:374 — SQL built from a string |
Observability & Operations
strongNo error reporter is wired in
adequateNothing in the service initialises an error reporter (Sentry, Rollbar, Bugsnag, Honeybadger or an APM agent). An exception in production reaches a person only if someone is reading the logs, which usually means a customer reports it first.
| no error reporter initialised |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on enterpilot/gomodel: 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.