fix: remediate vulnerable Python dependency floor - #11
Merged
Conversation
jason-allen-oneal
marked this pull request as ready for review
August 30, 2026 22:50
jason-allen-oneal
enabled auto-merge (squash)
August 30, 2026 22:55
morrow-bluedot
approved these changes
Aug 30, 2026
morrow-bluedot
left a comment
Contributor
There was a problem hiding this comment.
Independent exact-head review at 03fbbb8: the Python 3.10 floor and frozen lock remove all 20 vulnerable fallback entries. Audits are clean, 70 tests pass across supported interpreters, package metadata is coherent, and every hosted CI/CodeQL check succeeds.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
uv.lockgraph so the vulnerable Python 3.9 fallback packages are absentRoot cause
This remediation is pinned to default-branch commit
7a47b9f06ed50dffca06dbfa2c69060e95392109.All 20 open Dependabot alerts collapse to three Python 3.9 lockfile fallbacks:
The minimum fixed releases reported by GitHub require Python 3.10 or newer, while the project still declared Python 3.9 support. Raising both the project floor and the dependency floors removes the root cause instead of updating only the current environment.
Compatibility
Python 3.9 is no longer supported. Python 3.10, 3.11, and 3.13 remain in the CI matrix.
Validation
pip-audit 2.10.1audit of the exported lock graph on Python 3.10, 3.11, and 3.13: 0 known vulnerabilitiesuv sync --locked --all-extras: passed on Python 3.10, 3.11, and 3.13ruff check .: passed on all three interpretersRequires-Python: >=3.10and the patched dependency floorsScorecard alerts
Scorecard alert #7 (
VulnerabilitiesID) reports the same vulnerable Python 3.9 lock entries and is addressed by this dependency graph change.The four remaining open Scorecard SARIF alerts are not dismissed or hidden by this PR:
mainnow requires one approving review