Read 2026-11-03
matrixorigin/matrixone: technical due diligence, read from its repository
What Borehole read in matrixorigin/matrixone's code and history at d2451d5: 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 | adequate |
| 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
LICENSE: Relicensed: GPL-3.0 → Apache-2.0 (2021-09-07).gitmodules:1: 1 submodule(s) this survey does not read: third_party/sirius
Architecture & Codebase — including AI provenance
strongpkg/sql/plan/function/list_builtIn.go is 17,470 lines, 88× this codebase's median file
adequateThe median source file here is 197 lines. 119 files exceed 1,970 lines, the largest being 17,470. 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.
pkg/sql/plan/function/list_builtIn.go:1 — 17,470 lines (88× median) |
pkg/sql/parsers/dialect/mysql/mysql_sql.y:1 — 17,383 lines (88× median) |
pkg/sql/plan/query_builder.go:1 — 15,678 lines (79× median) |
pkg/sql/plan/function/func_binary.go:1 — 15,511 lines (78× median) |
thirdparties/cuda/Common/GL/glew.h:1 — 14,458 lines (73× median) |
Engineering Process & SDLC Maturity
adequate13% of recent commits change more than 2,000 lines
adequate570 of 4306 commits in the last 24 months changed over 2,000 lines of code, not counting reformatting, renames, vendored or generated code. A change that size is rarely reviewed line by line. Ask how they were reviewed, and what made them that large.
| 570 commits over 2,000 lines |
Product & Engineering Maturity
adequate122 direct dependencies in a single manifest
adequatego.mod declares 122 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 — 122 declared |
clients/python/pyproject.toml — 7 declared |
optools/tpch_compare/go.mod — 2 declared |
pkg/iceberg/adapter/iceberggo/go.mod — 1 declared |
Python 3.9 is past end of life
adequateThe code is pinned to Python 3.9 (end of life 2025-10-31). None of these receives security fixes any more; the first stopped on 2025-10-31. Moving off an unsupported runtime is rarely a one-line change, so a buyer should ask whether the upgrade is planned and what it touches.
optools/images/pythonserver/Dockerfile — Python 3.9, end of life 2025-10-31 |
Fixes are 72% of recent work, up from 44%
adequateIn the last two quarters 72% of commits were fixes, against 44% in the quarters before. Rising fix work usually means quality debt is coming due, and it takes time that new work would have had.
| 71%, 74%, 62%, 45%, 45%, 38%, 42%, 35% |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v4.2.7, is not on the branch this survey read; the newest release on it is v0.7.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v4.2.7 |
Security & Reliability Posture
adequate16 dependencies float, and no lockfile is committed
adequateDependency versions are declared as ranges and no lockfile is committed, so a build today does not necessarily produce what a build last month produced. That matters twice over in a transaction: the thing being bought cannot be reproduced exactly, and a compromised upstream release arrives without anyone choosing to take it.
clients/python/docs/requirements.txt:5 — >=4.0,<8.0 |
clients/python/docs/requirements.txt:6 — >=1.0,<3.0 |
clients/python/docs/requirements.txt:7 — >=2021.3.14 |
clients/python/docs/requirements.txt:10 — >=1.0.0,!=1.2.1,!=1.2.2,<1.3 |
clients/python/docs/requirements.txt:11 — >=0.2.0 |
3 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.
optools/bvt_ut/Dockerfile — runs as root |
optools/images/Dockerfile — runs as root |
optools/images/gpu/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate19 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/entrypoint.yaml:43 — action pinned by tag |
.github/workflows/entrypoint.yaml:120 — action pinned by tag |
6 outbound calls can wait forever
adequate6 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.
cmd/mo-debug/goroutine.go:227 — outbound call without a timeout |
pkg/util/metric/v2/dashboard/grafana_dashboard.go:589 — outbound call without a timeout |
pkg/util/metric/v2/dashboard/grafana_dashboard.go:646 — outbound call without a timeout |
93 SQL statements built from strings
adequate93 places in product code build SQL by formatting or joining strings rather than passing parameters, and in 13 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.
clients/python/matrixone/clone.py:87 — SQL built from a string |
clients/python/matrixone/clone.py:93 — SQL built from a string |
optools/range_scalar_bench.py:50 — SQL built from a string |
2 locked dependencies have published vulnerabilities, 4 high or critical in what ships
adequate2 of 304 locked dependencies match 4 published advisories in OSV, 4 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.
Observability & Operations
strongNo 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 |
4 of 12 deployed images carry no version, or `latest`
adequate4 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.
etc/docker-multi-cn-local-disk/docker-compose.yml:280 — image without a version |
etc/docker-multi-cn-local-disk/docker-compose.yml:320 — image without a version |
etc/launch-minio-local/docker-compose.yml:27 — 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 matrixorigin/matrixone: 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.