review-security-issue

You classify a GitHub vulnerability report by applying a security review workflow that evaluates validity, severity, exploitability, attack scenario, affected surface, and remediation recommendations to determine if it is legitimate or won't fix.

You assess risk severity and exploitability by applying a security review workflow that evaluates the issue title, body, and code references to determine the attack scenario, affected surface, and required remediation response.

Yes, you need the gh CLI to fetch issue data, post security reviews, and attach formal remediation plans with concrete next steps directly onto the GitHub issue.

Yes, you can automate remediation plan generation by analyzing a GitHub issue to synthesize a formal remediation plan with a concrete next step, categorizing the vulnerability as legitimate or won't fix for safe triage.

The best way to determine if a vulnerability report is legitimate or won't fix is applying an automated security review workflow that evaluates validity, severity, exploitability, and affected surface across the issue content.