Read 2026-10-22
redpanda-data/redpanda: technical due diligence, read from its repository
What Borehole read in redpanda-data/redpanda's code and history at 4254992: 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
Architecture & Codebase — including AI provenance
strongsrc/v/config/configuration.cc is 5,451 lines, 42× this codebase's median file
adequateThe median source file here is 129 lines. 60 files exceed 1,290 lines, the largest being 5,451. 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.
src/v/config/configuration.cc:1 — 5,451 lines (42× median) |
src/v/redpanda/admin/server.cc:1 — 5,178 lines (40× median) |
src/v/storage/disk_log_impl.cc:1 — 4,730 lines (36× median) |
src/v/raft/consensus.cc:1 — 4,461 lines (34× median) |
src/v/cluster/archival/ntp_archiver_service.cc:1 — 3,959 lines (30× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, v26.2.2, is not on the branch this survey read; the newest release on it is v26.1.1. The shipped product may differ from what this report describes. Survey the release branch too. This was read from the most recent 50,000 commits (9 Apr 2020 to 8 Oct 2026) only; older history was not read.
| tag v26.2.2 |
Security & Reliability Posture
adequate4 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. 17 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.
| 4 cited: JWT, where fakes are usual |
The build runs third-party code it does not pin
adequate18 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. 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/backport-command.yml:31 — action pinned by tag |
.github/workflows/backport-command.yml:35 — action pinned by tag |
9 locked dependencies have published vulnerabilities
adequate9 of 433 locked dependencies match 22 published advisories in OSV. 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.
bazel/packaging/go.mod — github.com/go-git/go-git/v5 v5.16.4: GHSA-37cx-329c-33x3 (moderate), fixed in 5.16.5 |
bazel/packaging/go.mod — github.com/ulikunitz/xz v0.5.12: GHSA-jc7w-c686-c4v9 (moderate), fixed in 0.5.15 |
bazel/thirdparty/Cargo.lock — wasmtime 42.0.2: GHSA-p8xm-42r7-89xg (moderate), fixed in 36.0.8 |
1 advisory against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2026-08-28. 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 26.1.1. Answer lives in: the release you run, set against each fixed version.
| 2026-08-28: CVE-2026-82266 (critical): Redpanda through 26.2.2 binds the Admin API to 0.0.0.0:9644 with admin_api_require_auth defaulting to false, treating unauthenticated requests as superusers. At |
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 redpanda-data/redpanda: 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.