pallets/flask: technical due diligence, read from its repository

The median source file here is 78 lines. 3 files exceed 1,000 lines, the largest being 1,629. 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.

Deleted lines per line added rose from 0.53 to 0.88 between the first and second halves of this history. Rework is normal and often healthy, but a rising ratio means an increasing share of the team's time is spent replacing code that already exists rather than building what does not. Whether that is deliberate repayment or churn is a question for the team.

3 of 83 locked dependencies match 8 published advisories in OSV, 6 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 development dependencies.

The newest was published on 2026-07-20. 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 1 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 3.1.3. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 62 records name flask with nothing tying them to this repository (CVE-2008-3687, CVE-2016-1000001, CVE-2018-16516, …).