Read 2026-10-28
ccfos/nightingale: technical due diligence, read from its repository
What Borehole read in ccfos/nightingale's code and history at 3b3e1ae: 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 | adequate |
| Observability & Operations | strong |
| Fit with the Acquirer | not assessable |
What the repository says
.github/PULL_REQUEST_TEMPLATE.md:8: states a policy on AI-generated contributions
Architecture & Codebase — including AI provenance
strongmodels/message_tpl.go is 3,953 lines, 26× this codebase's median file
adequateThe median source file here is 151 lines. 6 files exceed 1,510 lines, the largest being 3,953. 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.
models/message_tpl.go:1 — 3,953 lines (26× median) |
docker/initsql/a-n9e.sql:1 — 2,248 lines (14× median) |
pkg/ormx/database_init.go:1 — 2,025 lines (13× median) |
models/alert_rule.go:1 — 1,964 lines (13× median) |
alert/eval/eval.go:1 — 1,908 lines (12× 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: CI workflows. 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 1,880 tracked files |
Product & Engineering Maturity
adequateAPI v1 and v2 have been served together for 72 months
adequatev2 first appeared in Oct 2020, and v1 is still in the code 72 months later. Two versions mean two surfaces to secure, document and support. Ask who still calls the old one, and whether retiring it is planned.
src/modules/rdb/http/router.go — v1 since Sep 2020 |
src/modules/rdb/http/router.go — v2 since Oct 2020 |
Security & Reliability Posture
adequate3 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.
| 3 cited: JWT, where fakes are usual |
The build runs third-party code it does not pin
adequate5 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day; 1 step pipes a download straight into a shell. Tags have been moved to malicious commits in real supply-chain attacks, and a piped script is whatever the server returns that minute. Pinning to a commit is the fix, and it is small.
.github/workflows/issue-translator.yml:15 — action pinned by tag |
.github/workflows/n9e.yml:98 — action pinned by tag |
center/router/agentassets/collect-config.sh:29 — download piped into a shell |
6 SQL statements built from strings
adequate6 places in product code build SQL by formatting or joining strings rather than passing parameters. In each, what the code shows going in is a table or column name, a constant, or something the line does not show, not a request's value. Ask whether any value reaches these strings, rather than a parameter.
dskit/mysql/mysql.go:222 — SQL built from a string |
dskit/postgres/postgres.go:205 — SQL built from a string |
models/migrate/migrate.go:150 — SQL built from a string |
4 locked dependencies have published vulnerabilities, 4 high or critical in what ships
adequate4 of 211 locked dependencies match 7 published advisories in OSV, 4 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. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
14 workload settings give a container the host
adequate14 places in the deployment configuration run a container privileged or in the host's network, process or IPC namespace. A compromise of that container is a compromise of the machine, and most acquirers' security reviews block it. Node agents (network, storage, monitoring) are excluded.
docker/compose-host-network-metric-log/docker-compose.yaml:16 — privileged or host namespace |
docker/compose-host-network-metric-log/docker-compose.yaml:25 — privileged or host namespace |
docker/compose-host-network-metric-log/docker-compose.yaml:36 — privileged or host namespace |
2 advisories against this project in the last 24 months, 2 high or critical
adequateThe newest was published on 2026-09-04. 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 9.3.0. Answer lives in: the release you run, set against each fixed version.
| 2026-09-04: CVE-2026-85692 (high): Nightingale (n9e), as of commit 8362cbe (main branch, confirmed 2026-08-27), contains a server-side request forgery vulnerability in the isPublicIP function in |
| 2026-06-30: GHSA-27c6-wp53-387x (high), fixed in 6.7.3-0.20260528033214-762819fbaa23: Nightingale exposes datasource credentials to low-privilege users |
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 |
3 of 13 deployed images carry no version, or `latest`
adequate3 images in the deployment configuration are named without a version or as `latest`. A redeploy can change the software without a commit, a rollback has nothing to roll back to, and nobody can say from the repository what is running.
docker/compose-postgres/docker-compose.yaml:55 — image without a version |
docker/compose-postgres/docker-compose.yaml:81 — image without a version |
docker/compose-host-network-metric-log/docker-compose.yaml:28 — image without a version |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on ccfos/nightingale: 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.