apache/doris: technical due diligence, read from its repository

The median source file here is 118 lines. 208 files exceed 1,180 lines, the largest being 10,389. 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.

32 files were marked deprecated over two years ago and still are, the oldest since Feb 2023. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.

The newest release, 4.1.4, is not on the branch this survey read; the newest release on it is v0.8.2. The shipped product may differ from what this report describes. Survey the release branch too.

2 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; 1 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.

12 places in product code build SQL by formatting or joining strings rather than passing parameters. 1 of them put a value into the string; in the rest, what the code shows going in is a table or column name, a constant, or something the line does not show. Ask whether any value reaches these strings, rather than a parameter.

4 places read data with a deserialiser that executes what it reads (pickle, Java object streams). That is safe on data the system wrote itself and remote code execution on anything else. Ask where each one's input comes from.

15 of 286 locked dependencies match 64 published advisories in OSV, 28 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: some are pinned to a commit or a branch. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.

The newest was published on 2026-09-23. 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 9 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 0.8.2. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 1 record names doris with nothing tying it to this repository (CVE-2026-111692).

Nothing 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.