Pre-filter upstream-blocked container/image CVE findings before Copilot assignment - #53709
Merged
Merged
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Pre-filter upstream-blocked container/image CVE findings
Pre-filter upstream-blocked container/image CVE findings before Copilot assignment
Aug 18, 2026
pelikhan
marked this pull request as ready for review
August 18, 2026 14:37
Contributor
There was a problem hiding this comment.
Pull request overview
Adds upstream-versus-vendored triage to avoid assigning unfixable container findings locally.
Changes:
- Adds image ownership classification and remediation guidance.
- Adds a corresponding workflow evaluation.
- Regenerates the compiled workflow.
Show a summary per file
| File | Description |
|---|---|
.github/workflows/daily-squid-image-scan.md |
Adds triage instructions and evaluation. |
.github/workflows/daily-squid-image-scan.lock.yml |
Updates generated metadata and evaluations. |
Review details
- Files reviewed: 2/2 changed files
- Comments generated: 2
- Review effort level: Balanced
Comment on lines
+133
to
+136
| daily, so a pin refresh PR is the default remediation step). For findings | ||
| on **upstream** images, do not request a local code-fix PR or task an | ||
| agent to patch the vendored image directly — the daily pin-refresh | ||
| already picks up upstream fixes automatically once released. Instead, |
Comment on lines
+83
to
+84
| - id: upstream_vendored_triaged | ||
| question: Did the agent classify each finding as vendored (fixable in this repo) or upstream (owned by another repository), and avoid requesting a local code-fix PR for upstream-owned findings? |
Contributor
|
🎉 This pull request is included in a new release. Release: |
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.
Deep Report clustering analysis found "Container/Image Security Pinning" PRs merge 23 points below the fleet average — 12% of unmerged PRs in that cluster were tracking findings that were never actionable in this repo because the fix belongs upstream (
gh-aw-firewall, third-party MCP images).Changes
daily-squid-image-scan.md: added an explicit triage step that classifies each scanned image as:github/gh-aw, fixable locally.gh-aw-firewall,gh-aw-mcpg) or a third-party image (github-mcp-server,grafana/mcp-grafana,serena-mcp-server); no local code fix is possible.--force-refresh-container-pinscompile already absorbs upstream fixes once released.upstream_vendored_triagedto check that findings are correctly classified and upstream-owned findings don't trigger a local fix request..lock.ymlto match.Note: the stale-
[WIP]reaper portion of the original ask is already covered repo-wide by the existingdraft-pr-cleanup.mdworkflow (10-day warning / 14-day auto-close for inactive draft PRs), so no additional changes were needed there.