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

The median source file here is 105 lines. 68 files exceed 1,050 lines, the largest being 6,398. 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 (superset-frontend/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.

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

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

docker/.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.

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

3 places read data with a deserialiser that executes what it reads (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.

7 places set HTML from a value that is neither a literal nor passed through a sanitiser. Where the value can come from a user, that is stored cross-site scripting, and it is the first thing a buyer's security review looks for in a frontend.

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-07-30. 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 13 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.20.1. Answer lives in: the release you run, set against each fixed version. GHSA-w6c7-j32f-rq8j (moderate), GHSA-2cx9-54hp-r698 (moderate), GHSA-92qf-8gh3-gwcm (low) 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: 2 records name superset with nothing tying them to this repository (CVE-2024-32973, CVE-2026-97711).

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.

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