security-triage

Triage GitHub security advisories by verifying exact tags and commits, performing trust-model checks against SECURITY.md, and generating a maintainer-ready reply with concise verification notes.

Verify GHSA reports by running a full triage pass to assess advisories, check trust-models against SECURITY.md, and produce high-confidence close or keep recommendations with copy-ready maintainer replies.

Yes, you can generate a concise, copy-ready maintainer reply suitable for posting or sharing after verifying exact tag and commit information for the GitHub security advisory.

The trust-model check verifies advisory validity by comparing exact tag and commit information against the rules and sources defined in the project's SECURITY.md file to ensure high-confidence decisions.

Yes, exact tag and commit verification is required to produce high-confidence close or keep decisions for OpenClaw advisories, ensuring maintainer replies are backed by precise validation.

Yes, maintainers can use this triage process to validate security fixes before publishing by verifying commits and generating verification reports to ensure safe releases during a cycle.