What problem does it solve?
It helps maintainers quickly and accurately decide whether a GitHub security advisory should be closed or kept open, reducing both false closes and unnecessary regressions by verifying the exact shipped state and implicated code paths.
Core Features & Use Cases
- Evidence-driven close/keep decisions: Uses explicit criteria to close only when a duplicate, out-of-scope, already fixed before affected releases/tags, or invalid against shipped behavior is proven.
- Release/tag and commit verification: Guides verification of implicated fixes across git tags, tag containment, and npm published versions (including exact fix commit checks and optional file inspection).
- Trust-model and boundary checks: Prioritizes
SECURITY.md’s stated trust classes and prevents over-interpreting local/control-only issues as security boundary bypasses.
- Maintainer-ready response drafting: Produces a detailed reply template that includes the GHSA link, exact reasons, code references, shipped facts, and the final “copy to clipboard” step.
Quick Start
Use this skill to triage a GHSA by reading SECURITY.md, fetching the GHSA via the GitHub API, verifying the affected code paths and shipped tag/npm state, then drafting a maintainer-ready close reply in one copyable block.