fix(deps): remediate GitPython and AnyIO vulnerabilities - #1857
mldangelo-oai wants to merge 2 commits into
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Performance BenchmarksCompared
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 46986e664f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| RENOVATE_CONFIG = ROOT_DIR / "renovate.json" | ||
| PICKLESCAN_PYPROJECT = ROOT_DIR / "packages" / "modelaudit-picklescan" / "pyproject.toml" | ||
| PATCHED_GITPYTHON_FLOOR = (3, 1, 59) | ||
| PATCHED_GITPYTHON_FLOOR = (3, 1, 60) |
There was a problem hiding this comment.
Enforce the patched GitPython floor in package metadata
This guard only raises the version in uv.lock, which is not included in the published wheel's dependency metadata. The mlflow, all-ci, and all extras still declare only mlflow-skinny>=3.13.0; because that release already resolved successfully with GitPython 3.1.59 in the parent lock, an installation with 3.1.59 already present or constrained can retain the vulnerable version. Add GitPython>=3.1.60 to the relevant extras and make this regression test assert those declarations so the security floor also protects package consumers.
Useful? React with 👍 / 👎.
Summary: upgrade locked GitPython to 3.1.60 and AnyIO to 4.14.2, with regression floors for both security fixes.\n\nValidation: dependency-lock tests pass (22); formatting and lint checks pass; the CI-equivalent frozen-export dependency audit reports no known vulnerabilities.\n\nThe full uv lock resolver remains blocked by the existing PyTorch/CUDA index inconsistency for Python 3.13. This patch preserves the existing lock graph and uses verified lock artifacts.