Last week I wrote about a small trap: raising requires-python to 3.11 does not close the soupsieve alerts, because every fixed soupsieve release needs Python 3.11.5. I wanted to know how common this is, so I measured it.

What I checked

I took the 300 most-starred Python repos on GitHub that had a push this month. 94 of them use uv (they have a uv.lock), and I could analyze 92.

For each one I read the lock file, listed the vulnerable packages, and then asked PyPI a simple question: does any fixed release still install on the oldest Python this project supports? If the answer is no, no upgrade can close that alert. Someone has to decide to drop a Python version first.

Everything was read-only. I didn't run a resolver or change anything in anyone's project.

What I found

  • 70 of the 92 projects had open alerts.
  • 40 of those 70 (57%) have at least one vulnerable package that no fixed release reaches on their oldest supported Python.
  • Counting packages, it's 100 of 831 vulnerable packages (12%).

The packages behind it: soupsieve, filelock, pillow, dnspython, tornado, plus a few more. For the fixes, pillow, filelock, dnspython and tornado all need Python 3.11, and soupsieve needs 3.11.5.

The 3.11.5 trap

30 projects have a vulnerable soupsieve that they can't fix on their oldest Python. The part that surprised me: 13 of them already require Python 3.11, and they're still blocked, because 3.11.0 to 3.11.4 are still allowed.

Those 13 are manim, prefect, skyvern, airflow, graphrag, mlflow, serena, pydantic, python-telegram-bot, spotify-downloader, hindsight, wagtail and private-gpt.

For them, requires-python = ">=3.11" isn't enough. It has to be ">=3.11.5".

What this is not

This is not a criticism of any project. Supporting older Pythons is a fair choice, and some projects keep it on purpose. The point is that Dependabot or any other tool can't close these alerts by itself: someone has to decide.

Some limits, so you can judge the numbers:

  • The alerts come from pip-audit, not from Dependabot. They mostly agree, but not 100%.
  • "Blocked" comes from PyPI metadata, not from running a resolver. A project can still close an alert with an environment marker.
  • Counting alerts makes pillow look bigger (it has many advisories), so the per-package numbers are the fair ones.
  • It's one snapshot, from November 20, 2026.

Check it yourself

The scripts, the method and the data for every package are here: https://github.com/samuelrojas-dev/depquiet/tree/main/research/2026-11-python-floor

I measured this with depquiet, the tool I'm building. If you have alerts stuck like this, depquiet --fix-plan --raise-python-floor finds the exact floor (3.11.5, not 3.11) and checks it with uv or Poetry before you change anything.