feat(security-issue-sync): actionable admin hand-off relay for GHSA advisory changes#787
Merged
Conversation
…hanges github-advisory.md's Step 4 items 2 (state/publish/close) and 3 (collaborator management) are admin/security-manager operations the collaborator tier cannot perform; previously they were only 'surfaced' as a passive recap line. Add a concrete 'Admin hand-off relay' section: draft an email (never auto-sent) to the org's advisory-admin security team (security@apache.org for ASF), CC the project security list, naming what the sync already did, the admin-only change needed and why the collaborator tier can't, and the ask. Point Step 4 items 2 and 3 at it. Proven as a local override in an adopter repo; upstreaming per the override flow.
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
1 participant
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
github-advisory.md's Step 4 items 2 (state / publish / close) and 3 (collaborator management) are admin / security-manager operations the collaborator tier can't perform — the doc previously only told the sync to "surface it as a hand-off" (a passive recap line).This makes the hand-off actionable: a new "Admin hand-off — relay the needed change to the advisory-admin team" section. The sync drafts an email (never auto-sent) to the team that administers GitHub Private Vulnerability Reporting for the hosting org (for ASF,
security@apache.org), CC'ing the project security list, stating (1) what the sync already did at the collaborator tier with clickable…/security/advisories/GHSA-…URLs, (2) the exact admin-only change needed and why the collaborator tier can't (403), (3) the ask. Step 4 items 2 & 3 now point at it.Why
Learned running this in an adopter: the project's own security-team members usually don't hold GitHub advisory admin rights either, so @-mentioning them on the tracker leaves the action on nobody's desk. The request has to reach the org's advisory admins — an email relay, not a tracker comment.
Provenance
Proven as a local override in the
apache/airflowsecurity tracker, then upstreamed. First real use: relaying a "close this duplicate GHSA" request the collaborator tier403'd on.🤖 Generated with Claude Code