superbyte-ghsa-maintainer

To manage GitHub GHSA security advisories, you can fetch advisory states via the GitHub API, patch vulnerability payloads using jq, and transition publishing states with safety checks.

Validating a private fork's PRs before publishing a GHSA advisory works by verifying that no open pull requests exist in the linked private fork, ensuring a clean release process and safe state transition.

Yes, you can safely patch GHSA advisory data and validate payload shapes by applying JSON patching with jq and executing safety checks before transitioning the advisory state to published.

The best way to transition a GHSA advisory state to published is to fetch the advisory state, patch the vulnerability payload, verify no open PRs exist in the private fork, and then execute the publishing state transition with safety checks.

Yes, you need jq to perform JSON patching on GHSA advisories fetched via the GitHub API, allowing you to safely modify the vulnerability payload before validating and publishing.

Publishing a GHSA advisory fails when the private fork has open PRs because the workflow implements safety checks that verify a clean release process, blocking the state transition until the PRs are resolved.