Read 2026-10-22
neondatabase/neon: technical due diligence, read from its repository
What Borehole read in neondatabase/neon's code and history at fa50421: 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 | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
.gitmodules:1: 4 submodule(s) this survey does not read: vendor/postgres-v14, vendor/postgres-v15, vendor/postgres-v16
Architecture & Codebase — including AI provenance
strongpageserver/src/tenant.rs is 12,927 lines, 143× this codebase's median file
adequateThe median source file here is 90 lines. 74 files exceed 1,000 lines, the largest being 12,927. 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.
pageserver/src/tenant.rs:1 — 12,927 lines (143× median) |
storage_controller/src/service.rs:1 — 10,545 lines (117× median) |
pageserver/src/tenant/timeline.rs:1 — 8,327 lines (92× median) |
pageserver/src/metrics.rs:1 — 4,672 lines (51× median) |
pageserver/src/page_service.rs:1 — 4,663 lines (51× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, release-9129, is not on the branch this survey read. The shipped product may differ from what this report describes. Survey the release branch too.
| tag release-9129 |
Security & Reliability Posture
adequate1 credential-shaped string committed to the tree
adequateMatches for JWT appear in tracked files outside test and fixture paths. They stay in the history even after they leave the tree, so what matters is whether each was rotated. The code cannot tell whether any of them is live, and that decides whether this matters: none sits in production configuration, and none is in a format its provider keeps for live keys. Is any of these live? Show that each was rotated after it was committed, and when. 1 other match 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.
| JWT pattern matched |
The build runs third-party code it does not pin
adequate1 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.
build-tools/Dockerfile:192 — download piped into a shell |
47 locked dependencies have published vulnerabilities, 28 high or critical in what ships
adequate47 of 909 locked dependencies match 129 published advisories in OSV, 35 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.
poetry.lock — anyio 4.3.0: GHSA-82r6-8w77-94w6 (critical), fixed in 4.14.2 |
poetry.lock — certifi 2024.7.4: GHSA-6q48-6c7w-9gw2 (critical), fixed in 2026.10.19 |
poetry.lock — pyjwt 2.4.0: GHSA-ffc3-869f-jxw9 (critical), fixed in 2.14.0 |
1 vendored component with no licence
adequateThird-party code is committed into this repository without any statement of the terms it arrived under. Unknown terms are harder to deal with than inconvenient ones: an awkward licence can be complied with, an absent one cannot. Each of these needs its origin established before the code changes hands.
vendor/revisions.json — 1 tracked files, no licence file |
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 |
2 of 6 deployed images carry no version, or `latest`
adequate2 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/docker-compose.yml:14 — image without a version |
docker-compose/docker-compose.yml:182 — 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 neondatabase/neon: 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.