A small project with a vulnerable dependency that Dependabot cannot fix, and the pull requests depquiet opened to fix it.
requests==2.31.0 and botocore==1.29.0 are pinned on purpose. botocore 1.29.0 requires
urllib3<1.27, so every urllib3 fix (2.5.0 and later) needs botocore to move first.
Dependabot does not raise a parent package to fix a transitive one in Python projects
(dependabot-core#16337): it
reports that it cannot update the dependency to a non-vulnerable version, and the alerts
stay open.
pip-audit reports 10 alerts here: 3 in requests, 7 in urllib3.
The depquiet fixes workflow runs the depquiet
GitHub Action with fix-pr: "true". depquiet worked out that botocore has to move first
(to 1.44.5, on the run of 2026-11-18, with depquiet 0.48.0) for urllib3 to reach 2.8.0, checked with uv's resolver that every fix installs
together, and opened one pull request:
- uv project (this folder): pull request #1
- Poetry project (
poetry-app/), verified with Poetry's resolver: pull request #2
Each changes only the requirements and the lockfile. A scan after the change finds 0 alerts. depquiet checks that the versions resolve, not that the code works with them: urllib3 2 is a major version, so a real project would let its tests decide.
Copy .github/workflows/depquiet-fixes.yml, then
in Settings → Actions → General allow GitHub Actions to create pull requests. Run it
from the Actions tab. On your machine, depquiet --fix-plan shows the same plan
without changing anything:
pip install depquiet pip-audit
depquiet --fix-planDocs: depquiet README.