13 popular Python projects moved to 3.11 and still can't close their soupsieve alerts
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…
Last week, a report surfaced about 13 popular Python projects that have failed to close their soupsieve alerts after upgrading to Python 3.11. The underlying issue is that each fixed soupsieve release requires Python 3.11.5. To gauge the prevalence of this problem, I analyzed the 300 most-starred Python repositories on GitHub with updates this month, and found that 94 of them use uv.
Of those, 92 were analyzed, and 70 had open alerts. Out of these 70, 40 (57%) had at least one vulnerable package that couldn't reach a fixed release on their oldest supported Python version. When accounting for packages, this percentage rose to 12%. The culprits behind this issue are the soupsieve, filelock, pillow, dnspython, and tornado packages, with soupsieve needing Python 3.11.5.
What's surprising is that 13 projects already required Python 3.11 and were still unable to close the alerts, as 3.11.0 to 3.11.4 were still supported. These projects include manim, prefect, skyvern, airflow, graphrag, mlflow, serena, pydantic, python-telegram-bot, spotify-downloader, hindsight, wagtail, and private-gpt. They require a stricter version number (3.11.5) instead of just 3.11.
This situation highlights a limitation of automated tools like Dependabot, as they cannot close these alerts on their own. The alerts were collected using pip-audit, while the blocked status comes from PyPI metadata, not from running a resolver. While some projects may choose to support older Python versions, the fact remains that someone must decide to address this issue.
The figures presented are based on a single snapshot from November 20, 2026, and can be verified using the accompanying scripts and data on GitHub.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.