Repository navigation
fix: Upgrade certifi for GHSA-6q48-6c7w-9gw2 and add uv cooldown - #88
Merged
Merged
Conversation
There was a problem hiding this comment.
No issues found across 3 files
Confidence score: 5/5
- Automated review surfaced no issues in the provided summaries.
- No files require special attention.
Architecture diagram
sequenceDiagram
participant Dev as Developer
participant UV as uv (0.12.23)
participant PyPI as PyPI Registry
participant Lock as uv.lock
participant Cert as certifi Package
participant TC as Toolchain (asdf)
Note over Dev,TC: Dependency Resolution Flow
Dev->>TC: Install uv 0.12.23
TC->>TC: Read .tool-versions
TC-->>Dev: uv ready
Dev->>UV: uv lock (resolve deps)
UV->>UV: Read [tool.uv] config
alt Package is certifi
UV->>UV: Check exclude-newer-package
UV-->>UV: certifi exempt (temporary)
else Other packages
UV->>UV: Apply 7-day exclude-newer window
end
UV->>PyPI: Query package metadata
PyPI-->>UV: Versions with upload dates
UV->>UV: Filter recent (<7 days) unless exempt
UV->>Lock: Write resolved versions
Lock-->>UV: Updated lockfile
Note over Dev,Lock: CI / Build Flow
Dev->>UV: uv sync (install from lock)
UV->>Lock: Read locked versions
Lock-->>UV: certifi 2026.10.19 (patched)
UV->>PyPI: Download wheels
PyPI-->>UV: Patched certifi
UV-->>Dev: Installed environment
Note over UV,PyPI: Security Boundary: supply-chain cooldown blocks compromised uploads before they reach lockfile
wgrant
approved these changes
Oct 20, 2026
sontek
approved these changes
Oct 20, 2026
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
Upgrade certifi to 2026.10.19 to fix GHSA-6q48-6c7w-9gw2.
Add a 7-day
exclude-newerwindow to[tool.uv]. uv now refusespackage versions uploaded less than 7 days ago. certifi is exempt
from the window so we can take the fix now. A comment marks the
exemption as temporary, for removal on the next certifi upgrade.
The relative
exclude-newervalue and the per-package exemption needa newer uv, so
.tool-versionsmoves uv to 0.12.23. The lockfilerefresh also picks up minor upgrades of other dependencies.
why
certifi 2026.7.22 is vulnerable to GHSA-6q48-6c7w-9gw2.
The cooldown is a supply-chain defence. A compromised release that
lands on PyPI cannot enter the lockfile before maintainers and
detection tools have time to react.
testing
Relying on the existing suite against the refreshed lockfile.
docs
No docs needed.
🤖 Generated with Claude Code