taosdata/tdengine: technical due diligence, read from its repository

45% of commit subjects are exact repeats of another subject, and subject length varies by only 21.1 characters. A log written by someone explaining their reasoning to a future reader does not look like this. The log is therefore weak evidence of intent, whatever the code is like. This was read from the most recent 50,000 commits (5 Aug 2022 to 19 Oct 2026) only; older history was not read.

The median source file here is 224 lines. 111 files exceed 2,240 lines, the largest being 25,140. 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.

7 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; 5 steps pipe 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.

2 places run a command through a shell (`shell=True`, `os.system`, `exec` with a template) rather than passing arguments. Where any part comes from outside, it is command injection. Ask where each one's input comes from.

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

The newest was published on 2026-06-27. 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 14 of them are fixed in the code you ship could not be told from this history. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 1 record names TDengine with nothing tying it to this repository (CVE-2026-47720).

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.