openclaw-ghsa-maintainer

Automating GitHub Security Advisories patching involves inspecting advisory state, validating private fork status, assembling Markdown and JSON payloads, applying separate PATCH calls in sequence, and verifying publication before completing the workflow.

Validating private fork status before publishing a GHSA involves inspecting the advisory state, verifying that no open pull requests exist in the private fork, and ensuring all guardrail safety checks pass before applying the final publication PATCH.

Assembling Markdown and JSON payloads for the GitHub Security Advisories API requires safely preparing content and applying separate PATCH calls in the required order to update advisory metadata and documentation without conflicts.

Yes, the GitHub Security Advisories API supports automated guardrail checks by enforcing advisory usage policies and safety validations before any publish action, ensuring vulnerabilities and advisory states are handled consistently.

Separate PATCH calls fail when patching GitHub Security Advisories payloads if guardrail safety checks are not satisfied, the private fork has open pull requests, or the Markdown and JSON payload sequence is applied out of the required order.

This advisory maintainer workflow is specifically designed to inspect, patch, validate, and publish GitHub Security Advisories for the OpenClaw project, conforming to its specific guardrails for consistent vulnerability handling.