Read 2026-10-04
nats-io/nats-server: technical due diligence, read from its repository
What Borehole read in nats-io/nats-server's code and history at 60b9679: 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
.github/PULL_REQUEST_TEMPLATE.md:1: states a policy on AI-generated contributionsREADME.md:5: names Cloud Native Computing Foundation
Architecture & Codebase — including AI provenance
strongserver/filestore.go is 14,733 lines, 46× this codebase's median file
adequateThe median source file here is 317 lines. 17 files exceed 3,170 lines, the largest being 14,733. 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.
server/filestore.go:1 — 14,733 lines (46× median) |
server/jetstream_cluster.go:1 — 14,424 lines (45× median) |
server/stream.go:1 — 9,802 lines (30× median) |
server/consumer.go:1 — 7,329 lines (23× median) |
server/client.go:1 — 7,128 lines (22× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest pre-release, v2.15.1-RC.1, is not on the branch this survey read; the newest release on it is v2.15.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v2.15.1-RC.1 |
Security & Reliability Posture
adequate3 credential-shaped strings 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.
| 3 cited: JWT pattern matched |
28 advisories against this project in the last 24 months, 13 high or critical
adequateThe newest was published on 2026-06-29. 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 2.15.0. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 1 record names nats-server with nothing tying it to this repository (CVE-2021-3127).
| 2026-06-29: GHSA-q59r-vq66-pxc2 (high), fixed in 2.12.12: Remote crash via integer overflow in Connz pagination |
| 2026-06-29: GHSA-p957-7v2w-g93g (moderate), fixed in 2.12.12: MQTT-over-WebSocket Path Can Crash WebSocket-Only JetStream Servers Before MQTT Is Enabled |
| 2026-06-29: GHSA-7qmq-8cc4-hxwg (moderate), fixed in 2.12.12: MQTT retained and QoS replay bypass subscribe deny filters |
| 2026-06-29: GHSA-r72h-j7qq-v6qg (high), fixed in 2.12.12: MQTT partial CONNECT packets can exhaust pre-auth memory |
| 2026-06-29: GHSA-hmmp-q8cx-v964 (moderate), fixed in 2.12.12: `no_auth_user` pre-CONNECT fast path bypasses user connection restrictions |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 421 readable files references an instrumentation, metrics or error-reporting library. If this system is in production, nobody learns that it broke from the system itself — they learn it from a customer. That is a reliability finding before it is an observability one.
| searched 421 tracked text files for 16 known instrumentation libraries; manifests for metrics, tracing and error-reporting families; locked dependencies for the packages that emit; 0 matched |
No structured logging library is in use
adequateNothing references a structured logging library. Logs that are written to be read by a person are not searchable by a machine, which means incident response here is proportional to how well someone remembers the codebase rather than to what the tooling can find.
| searched 421 files for 10 structured logging libraries; 0 matched |
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 nats-io/nats-server: 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.