Read 2026-10-22
vitessio/vitess: technical due diligence, read from its repository
What Borehole read in vitessio/vitess's code and history at e97e54f: 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 | adequate |
| 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
- Releases are cut from another branch than the one surveyed
.github/pull_request_template.md:48: states a policy on AI-generated contributionsREADME.md:6: names OpenSSF
Architecture & Codebase — including AI provenance
adequatego/mysql/collations/charset/simplifiedchinese/tables.go is 43,998 lines, 354× this codebase's median file
adequateThe median source file here is 124 lines. 70 files exceed 1,240 lines, the largest being 43,998. 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.
go/mysql/collations/charset/simplifiedchinese/tables.go:1 — 43,998 lines (354× median) |
go/mysql/collations/charset/korean/tables.go:1 — 34,151 lines (275× median) |
go/vt/sqlparser/ast_rewrite.go:1 — 16,449 lines (132× median) |
go/vt/sqlparser/sql.y:1 — 9,738 lines (78× median) |
go/vt/sqlparser/ast_copy_on_rewrite.go:1 — 9,072 lines (73× median) |
1 base image floats: no version, or `latest`
adequate1 of 36 `FROM` lines in product Dockerfiles name an image without a version, or with `latest`. Each build pulls whatever the registry serves that day, so the image that ships can change without a commit, and last month's build cannot be reproduced. Pin a version, or a digest.
docker/mini/Dockerfile:15 — base image without a version |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate94 direct dependencies in a single manifest
adequatego.mod declares 94 direct dependencies. Each one is a maintenance obligation, a supply-chain surface and a potential licence question that transfers with the asset. The count says nothing about whether any given dependency was a good choice; it says how many such choices a buyer inherits.
go.mod — 94 declared |
web/vtadmin/package.json — 23 declared |
5 files still carry code deprecated more than two years ago
adequate5 files were marked deprecated over two years ago and still are, the oldest since Nov 2022. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.
go/cmd/vtctldclient/command/reparents.go — deprecated since Nov 2022 |
go/vt/vtgate/grpcvtgateconn/conn.go — deprecated since Feb 2023 |
go/mysql/icuregex/internal/normalizer/constants.go — deprecated since Jul 2023 |
go/mysql/icuregex/internal/unames/unames.go — deprecated since Jul 2023 |
go/mysql/icuregex/internal/uprops/uprops_int.go — deprecated since Jul 2023 |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v24.0.5, is not on the branch this survey read; the newest release on it is v10.0.2. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v24.0.5 |
Security & Reliability Posture
adequate13 Dockerfiles run the application as root
adequateNo USER instruction switches away from root, so the process runs with full privileges inside the container. It is a one-line fix and an ordinary expectation, which is why its absence is worth asking about: it usually says more about whether anyone has reviewed the deployment than about this container specifically.
docker/binaries/logrotate/Dockerfile — runs as root |
docker/binaries/logtail/Dockerfile — runs as root |
docker/binaries/mysqlctl/Dockerfile — runs as root |
docker/binaries/mysqlctld/Dockerfile — runs as root |
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.
web/vtadmin/build.sh:51 — download piped into a shell |
11 outbound calls can wait forever
adequate11 HTTP calls use a client with no timeout (Python `requests` without `timeout=`, or Go's default client). When a dependency slows down, each one holds a worker until the connection gives up, and enough of them take the service down with the dependency.
go/stats/opentsdb/init.go:96 — outbound call without a timeout |
go/vt/vtctl/grpcvtctldserver/server.go:5809 — outbound call without a timeout |
go/vt/vttablet/endtoend/framework/debugschema.go:46 — outbound call without a timeout |
10 SQL statements built from strings
adequate10 places in product code build SQL by formatting or joining strings rather than passing parameters, and in 5 of them a value, not a table or column name, goes into the string. Where any of those values comes from a request, it is an injection point. Each site needs a look; the fix, parameters, is small.
go/vt/vtctl/workflow/stream_migrator.go:474 — SQL built from a string |
go/vt/vtctl/workflow/stream_migrator.go:579 — SQL built from a string |
go/vt/vttablet/tabletmanager/vdiff/table_differ.go:215 — SQL built from a string |
26 advisories against this project in the last 24 months, 19 high or critical
adequateThe newest was published on 2026-10-13. 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 2 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 10.0.2. Answer lives in: the release you run, set against each fixed version. GHSA-m282-7w35-g77m (high), GHSA-9248-hccp-qf8f (high), GHSA-9rx3-8pwm-c228 (high) and 12 more are fixed in the surveyed commit; which release carries them cannot be told from this history, which does not place the release users run. Answer lives in: the version you run.
| 2026-10-13: GHSA-92cc-q2h6-m2vr (high), fixed in 23.0.8: Vitess is vulnerable to SQL injection via convert_tz() arguments in a VStream filter written into the copy-phase snapshot query |
| 2026-10-13: GHSA-m282-7w35-g77m (high), fixed in 23.0.8: Vitess is vulnerable to SQL injection via an unvalidated global SET variable name re-emitted into a VTTablet validation query |
| 2026-10-13: GHSA-9248-hccp-qf8f (high), fixed in 23.0.8: Vitess is vulnerable to SQL injection via AST re-serialization of DATE, TIME and TIMESTAMP literals in SET system-variable statements |
| 2026-10-13: GHSA-9rx3-8pwm-c228 (high), fixed in 23.0.8: Vitess is vulnerable to SQL injection via a session system variable value that breaks out of the SET_VAR optimizer-hint comment |
| 2026-10-13: GHSA-pfg5-ppc7-ff45 (high), fixed in 23.0.8: Vitess is vulnerable to SQL injection via trailing-comment splitting that hides SQL from parsing, planning and ACL checks |
Observability & Operations
strongNo finding.
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on vitessio/vitess: 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.