datahub-project/datahub: technical due diligence, read from its repository

The median source file here is 81 lines. 163 files exceed 1,000 lines, the largest being 5,466. 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.

The suite is configured to retry failing tests (e2e-test/ui/playwright/playwright.config.ts). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.

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

datahub-web-react/.env is tracked in git. Environment files are where credentials usually live, and committing one usually means nobody decided how secrets reach the running application. Whatever is in it is in the history for good. Check 05.1 says whether it holds anything credential-shaped.

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

45 places in product code build SQL by formatting or joining strings rather than passing parameters. 4 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.

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.

3 places read data with a deserialiser that executes what it reads (`yaml.load` without a safe loader, 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.

108 of 3,530 locked dependencies match 192 published advisories in OSV, 110 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: they are optional extras of a package, installed only on request. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.

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-05-19. 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 1.4.0. Answer lives in: the release you run, set against each fixed version. GHSA-3p57-xxv6-6wqp (moderate), GHSA-phm8-vwjg-f442 (moderate) 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. The record is incomplete: NVD: 18 records name datahub with nothing tying them to this repository (CVE-2011-3493, CVE-2011-3500, CVE-2011-3501, …).

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