Read 2026-10-23
prometheus/alertmanager: technical due diligence, read from its repository
What Borehole read in prometheus/alertmanager's code and history at 294c544: 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
- Releases are cut from another branch than the one surveyed
Architecture & Codebase — including AI provenance
strongapi/v2/restapi/embedded_spec.go is 1,838 lines, 14× this codebase's median file
adequateThe median source file here is 125 lines. 1 file exceed 1,250 lines, the largest being 1,838. 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.
api/v2/restapi/embedded_spec.go:1 — 1,838 lines (14× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, v0.34.1, is not on the branch this survey read; the newest release on it is v0.34.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v0.34.1 |
Security & Reliability Posture
adequate7 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. 2 other matchs set aside: expired tokens, licence tokens a vendor verifies with a public key, or placeholder text where a key would go. None grants access to anything.
| 5 cited: Slack token, where fakes are usual |
1 advisory against this project in the last 24 months
adequateThe newest was published on 2026-08-13. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 1 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 0.34.0. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 3 records name alertmanager with nothing tying them to this repository (CVE-2025-3454, CVE-2026-17033, CVE-2026-21723).
| 2026-08-13: CVE-2026-67990 (moderate): basecamp/upright at commit efe4f2e5254ac6e57e45d2261804cca74dbbca3f disables Rails CSRF protection for its Alertmanager and Prometheus proxy controllers. An una |
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 prometheus/alertmanager: 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.