sincecutoff.com
← all changes

gh GraphQL securityAdvisories adds severity and withdrawal filters

Introduced 2026-10-02 · score 0.98

HOW TO USE IT

For severity triage or a withdrawn-advisory audit, call `securityAdvisories` with the relevant `severities` or `isWithdrawn` filter and select the advisory fields you need.

gh api graphql -F 'severities[]=HIGH' -f query='query($severities: [SecurityAdvisorySeverity!]) { securityAdvisories(severities: $severities, first: 100) { nodes { ghsaId severity summary } } }'
gh api graphql -F isWithdrawn=true -f query='query($isWithdrawn: Boolean) { securityAdvisories(isWithdrawn: $isWithdrawn, first: 100) { nodes { ghsaId severity summary withdrawnAt } } }'

WHY THIS HELPS

Narrow advisory results for a severity-based triage feed or withdrawn-advisory audit.

BEFORE THIS CHANGE

The release note says integrations previously downloaded results and filtered them client-side.

REQUIREMENTS AND LIMITATIONS

  • severities: List of advisory severities to filter by; values: `CRITICAL`, `HIGH`, `LOW`, `MODERATE`, `UNKNOWN`.
  • isWithdrawn: `true` returns only withdrawn advisories; `false` excludes withdrawn advisories.
  • gh api graphql (required): `gh api` makes an authenticated API request; `graphql` selects GitHub API v4.
  • -F, --field <key=value>: Adds a typed parameter; for GraphQL, fields other than `query` and `operationName` are variables. Supports array fields with `key[]=value`.
  • -f, --raw-field <key=value> (required): Adds a string parameter; used here to pass the GraphQL query.
  • Prerequisite: `gh api` makes authenticated requests; this task needs an authenticated GitHub CLI session.
  • The new filters work alongside existing filters, including classification, identifier, EPSS, and published or updated since.
  • The changes are additive and read-only; existing queries keep working.

FIRST-PARTY EVIDENCE

Check the installed version and the source before using it. Entry JSON

Report a problem with this card