Raising the minimum supported Python version in a project does not always clear security alerts for dependencies. A recent review of the 300 most-starred Python repositories on GitHub, all with recent activity, showed that updating requires-python to 3.11 often leaves vulnerability warnings unresolved—especially for the soupsieve package. The Requires-Python field in package metadata sets the minimum interpreter version for installation. This field directly affects whether a project can move to a patched dependency release.
Understanding the Version Trap
Out of 92 actively maintained repositories using uv.lock files, 70 still had open vulnerability alerts. In 40 of these, at least one vulnerable package could not be upgraded to a fixed release that works with the oldest Python version the project supports. If a project keeps support for older Python versions, no automated tool can close the alert. Changing the minimum Python version does not guarantee that every dependency vulnerability will be fixed. A dependency may stay blocked if the patched release has stricter interpreter metadata or if another package pins an incompatible version.
The soupsieve case is even tighter. All fixed releases of soupsieve require Python 3.11.5 or newer. This leaves 30 projects stuck with a vulnerable version they cannot upgrade on their current Python floor. Thirteen of these projects already require Python 3.11, but their requirement allows any 3.11.x version—including 3.11.0 through 3.11.4, which do not meet the patched soupsieve releases. These projects include manim, prefect, skyvern, airflow, graphrag, mlflow, serena, pydantic, python-telegram-bot, spotify-downloader, hindsight, wagtail, and private-gpt. For these, setting requires-python = ">=3.11" is not enough. The requirement must be raised to ">=3.11.5" to allow installation of a fixed soupsieve version. The technical difference is that >=3.11 permits all Python 3.11 patch releases, while >=3.11.5 excludes earlier 3.11 releases, which is necessary for compatibility with patched dependencies.
Other Packages with Similar Issues
The review also found that packages like pillow, filelock, dnspython, and tornado require Python 3.11 for their fixed releases. Out of 831 vulnerable packages across the reviewed projects, 100 (about 12%) could not be upgraded to a secure version on the oldest supported Python version. Package compatibility requirements can vary by release, extras, operating system, and resolver policy. Maintainers need to check the specific requirements of each dependency update. Python package compatibility and vulnerability status depend on the combination of package metadata, advisory databases, and the dependency resolver's behavior.
Why Automated Tools Cannot Always Help
Tools such as Dependabot and pip-audit can spot vulnerabilities, but they cannot resolve alerts when no fixed package version matches the project's Python floor. In these cases, a project maintainer must choose whether to drop support for older Python versions or accept the unresolved alert. The data in this review was collected using depquiet, which can pinpoint the exact Python version needed to close a given alert. Automated tools rely on the metadata and lockfile constraints present at the time of analysis. Repository dependency declarations and lockfiles can change over time.
How to Check Your Project
If your project faces persistent dependency alerts, you can use depquiet --fix-plan --raise-python-floor to find the minimum Python version needed for a secure upgrade. This method checks compatibility with tools like uv or Poetry before making changes. For more on dependency management and Python project maintenance, see this earlier breakdown. For official guidance on Python packaging and dependency management, refer to the Python Packaging Authority documentation.
