fix(ci): remove stale vulnerability ignores — all CVEs now fixed upstream#148
fix(ci): remove stale vulnerability ignores — all CVEs now fixed upstream#148JacobPEvans merged 1 commit intomainfrom
Conversation
…ream - pygments 2.20.0 (released 2026-03-29) fixes CVE-2026-4539 (GHSA-5239-wwwm-4pmq); remove --ignore-vuln flag from _python-security.yml pip-audit command - nltk 3.9.4 fixes GHSA-jm6w-m3j8-898g, GHSA-rf74-v2fm-23pw, GHSA-gfwx-w7gr-fvh7; already upgraded, advisory DB entries now stale - requests 2.33.0 fixes GHSA-gc5v-m9x4-r6x2; already upgraded - osv-scanner.toml now contains only the header comment block (no active ignores) (claude)
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request cleans up security configuration files by removing outdated vulnerability ignore rules. With recent upstream dependency updates, these previously ignored CVEs are now resolved, allowing for a cleaner and more secure CI environment. Highlights
Ignored Files
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. The vulnerabilities are gone at last, / The stale ignores are in the past. / With versions new and patches applied, / Our code is safe and fortified. Footnotes
|
There was a problem hiding this comment.
Pull request overview
This PR removes now-unnecessary vulnerability ignore configuration from the org-wide security scanning setup after upstream fixes landed, keeping CI enforcement strict and up-to-date.
Changes:
- Removed the
--ignore-vulnexception (and related comment block) from the reusablepip-auditworkflow. - Cleared all stale
[[IgnoredVulns]]entries from the centralosv-scanner.toml, leaving only the header comments.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
.github/workflows/_python-security.yml |
Stops suppressing a previously-unpatched GHSA in pip-audit, so the audit runs cleanly without exceptions. |
osv-scanner.toml |
Removes stale OSV ignore entries while retaining the central config file for inherited scanning behavior. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Summary
--ignore-vulnflag from the_python-security.ymlpip-audit command and the 3-line comment block above itosv-scanner.tomlnow contains only the header comment block with no active[[IgnoredVulns]]entriesFiles Changed
.github/workflows/_python-security.yml— remove pygments CVE ignore flag and associated comments;uvx pip-auditcommand is now cleanosv-scanner.toml— remove all 5 stale[[IgnoredVulns]]entries; keep file with header comment only (required for_osv-scan.ymlfallback mechanism)Test plan
🤖 Generated with Claude Code