Read 2026-10-04
valkey-io/valkey: technical due diligence, read from its repository
What Borehole read in valkey-io/valkey's code and history at dca022f: 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 | strong |
| Observability & Operations | adequate |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
README.md:2: names OpenSSF
Architecture & Codebase — including AI provenance
strongsrc/module.c is 15,932 lines, 116× this codebase's median file
adequateThe median source file here is 137 lines. 57 files exceed 1,370 lines, the largest being 15,932. 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/module.c:1 — 15,932 lines (116× median) |
src/valkey-cli.c:1 — 10,298 lines (75× median) |
src/cluster_legacy.c:1 — 9,555 lines (69× median) |
src/server.c:1 — 8,417 lines (61× median) |
src/networking.c:1 — 7,312 lines (53× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongReleases are cut from another branch than the one surveyed
adequateThe newest release, 9.1.2, is not on the branch this survey read; the newest release on it is 8.0.8. The shipped product may differ from what this report describes. Survey the release branch too.
| tag 9.1.2 |
Security & Reliability Posture
strong1 deserialiser that can run code
adequate1 places read data with a deserialiser that executes what it reads (pickle). That is safe on data the system wrote itself and remote code execution on anything else. Ask where each one's input comes from.
deps/gtest-parallel/gtest_parallel.py:627 — code-executing deserialiser |
1 locked dependency has published vulnerabilities, 2 high or critical
adequate1 of 5 locked dependencies match 3 published advisories in OSV, 2 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. None of the high or critical ones is in what the product ships: only the build reaches them: a bundler, a code generator, a build plugin, or a lockfile in a tooling directory.
utils/reply-schema-linter/package-lock.json — fast-uri 3.1.6: GHSA-58mr-gqgx-xq4g (high), fixed in 3.1.7; reached only by the build |
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.
deps/README.md — 1 tracked files, no licence file |
18 advisories against this project in the last 24 months, 9 high or critical
adequateThe newest was published on 2026-09-06. 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 11 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 8.0.8. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 3 records name valkey with nothing tying them to this repository (CVE-2026-54246, CVE-2026-78551, CVE-2026-84372).
| 2026-09-06: CVE-2026-86227 (low): A weakness has been identified in valkey-io valkey up to 9.0.5/9.1.1. This affects the function kvstoreGetHashtable of the file src/kvstore.c. This manipulation |
| 2026-09-04: CVE-2026-85522 (moderate): A vulnerability was detected in valkey-io valkey up to 9.5.4/9.1.0. Affected by this vulnerability is the function createSlotImportJob of the file src/cluster_m |
| 2026-08-31: GHSA-jcj7-v34w-v9vv (high), fixed in 8.0.11: Use-after-free in the RDMA pending-data handler when a client |
| 2026-08-31: GHSA-fq2f-crmw-q97r (high), fixed in 9.1.2: Unauthenticated use-after-free of the Lua interpreter state in Valkey (script debugger command cache) |
| 2026-08-31: CVE-2026-82631 (low): A security flaw has been discovered in valkey-io valkey 9.1.0. The affected element is the function handleClientsBlockedOnKey of the file src/blocked.c of the c |
Observability & Operations
adequateNo telemetry or error reporting is wired in anywhere
adequateNone of 1,932 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 1,932 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.
| C source is not searched: C programs log through printf-style calls unless they take a library, and none of the 10 searched for is referenced |
One 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 valkey-io/valkey: 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.