Read 2026-11-03
prometheus/node_exporter: technical due diligence, read from its repository
What Borehole read in prometheus/node_exporter's code and history at 2ae7dd8: 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 | adequate |
| Security & Reliability Posture | strong |
| Observability & Operations | adequate |
| 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
strongcollector/netstat_descs_linux.go is 1,263 lines, 10× this codebase's median file
adequateThe median source file here is 119 lines. 1 file exceed 1,190 lines, the largest being 1,263. 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.
collector/netstat_descs_linux.go:1 — 1,263 lines (10× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate14% of bug fixes add or change a test
adequateOf 49 fixes in the last 24 months, 7 touched a test. A fix without the test that would have caught the bug can quietly come back, and the suite never learns from what went wrong.
| 7 of 49 |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v1.12.1, is not on the branch this survey read; the newest release on it is v1.12.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v1.12.1 |
Security & Reliability Posture
strongNo finding.
Observability & Operations
adequateOne request cannot be followed through the logs
adequateNothing in the service carries a request or correlation id, and there is no tracing. When a customer reports a failure, the log lines that belong to their request cannot be picked out from everyone else's.
| no request id, correlation id or tracing found |
No 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 prometheus/node_exporter: 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.