security-triage

Triage GitHub security advisories by verifying affected tags and commits, applying trust-model checks, and evaluating advisory content against the shipped state to produce high-confidence close or keep decisions.

Yes, you can generate a formatted reply suitable for clipboard posting after triaging a GitHub security advisory, which includes the close/keep decision, verification results, and optional hardening notes.

A trust-model check verifies the integrity and origin of affected tags and commits in GitHub security advisories, ensuring that correct remediation mapping is applied before making a close or keep decision.

Yes, this advisory triage process works with GHSA reports, draft advisories requiring verification, and OpenClaw-related advisories to generate high-confidence decisions and ready-to-post replies.

Verify affected tags and commits by mapping the advisory content to the actual shipped state of the repository, ensuring exact remediation mapping and validating the results through trust-model checks.

The best way to add hardening notes is to include them as optional guidance for maintainers within the final formatted triage reply, generated after completing the close or keep decision and commit verification.