Read 2026-10-23
ergo-services/ergo: technical due diligence, read from its repository
What Borehole read in ergo-services/ergo's code and history at 301097b: 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 | not assessable |
| Security & Reliability Posture | adequate |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
strongnet/proto/connection.go is 4,183 lines, 28× this codebase's median file
adequateThe median source file here is 149 lines. 5 files exceed 1,490 lines, the largest being 4,183. 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.
net/proto/connection.go:1 — 4,183 lines (28× median) |
node/node.go:1 — 3,309 lines (22× median) |
node/process.go:1 — 2,392 lines (16× median) |
node/network.go:1 — 1,899 lines (12× median) |
node/core.go:1 — 1,661 lines (11× median) |
Engineering Process & SDLC Maturity
adequatePinned dependencies have not moved in 79 months
adequateThe lockfile last changed 2382 days before the newest commit, and 94 commits have landed since. Every security fix published upstream in that time is absent until someone updates it, and the longer the gap the larger and riskier that update becomes.
| go.sum last changed 2020-02-28 |
Product & Engineering Maturity
not assessableNot rated: only 9 of 19 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
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 496 tracked files; 0 present |
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 ergo-services/ergo: 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.