GitHub has expanded its SecurityAdvisory GraphQL API to supply additional advisory metadata directly within single queries, reducing the reliance on REST API fallbacks for security integration workflows.
New Metadata Fields for Security Advisories
The GraphQL API update introduces five new fields to the SecurityAdvisory object. Integrations can now retrieve an advisory's official CVE identifier via cveId, access direct references to affected code through sourceCodeLocation, and view the linked repository security advisory via repositoryAdvisoryUrl.
Additionally, GitHub added precise timestamp tracking to the object. Queries can request githubReviewedAt to check when GitHub completed its review, alongside nvdPublishedAt to inspect when the National Vulnerability Database published its record.
Server-Side Query Filtering
To streamline data extraction, the securityAdvisories query gained two dedicated server-side filters: severities and isWithdrawn. These additions allow applications to filter results on GitHub's servers rather than fetching broad dataset payloads for client-side processing.
The new arguments complement existing query filters, including classification, identifier, EPSS score, and update timestamps. By enabling targeted queries, developers can construct focused pipelines such as severity-based triage feeds and audit trails for withdrawn advisories.
Workflow Efficiency and API Mechanics
By consolidating advisory attributes into the GraphQL interface, integrations operate under a unified authentication model and a single rate-limit budget. The addition of direct fields reduces network round trips between GitHub's endpoints and external security platforms.
All schema updates are read-only and additive, ensuring backwards compatibility for existing GraphQL queries without breaking active developer implementations.
AI-generated editorial illustration; not a documentary photograph.
Source: New fields for SecurityAdvisory GraphQL API
SIGNAL TITANS
Leave a Reply