GitHub Rolls Out Code Quality Findings REST API in Preview

GitHub has introduced two new repository-level REST API endpoints for fetching Code Quality findings, now available in public preview as of June 23, 2026. This move brings the automation capabilities closer to what developers already access via the GitHub user interface, improving integration options for CI/CD pipelines, dashboards, and third-party tools.

The two new read-only endpoints allow administrators and developers to programmatically retrieve Code Quality findings for repositories. This aligns with GitHub’s broader push to make its Code Quality feature set more accessible and configurable through APIs. The announcement follows the earlier release of the Repository Enablement API in May 2026, which allowed users to enable and configure Code Quality directly through REST API calls.

GitHub Code Quality scans include both “Standard findings”—results from CodeQL rule-based analysis—and “AI findings,” which leverage machine learning to assess recently pushed files. These findings are displayed in the “Security and quality” tab of repositories. Importantly, during the ongoing public preview phase, scans consume GitHub Actions minutes but are not otherwise billed. Billing will begin when the feature becomes generally available on July 20, 2026.

The APIs are versioned (e.g., X-GitHub-Api-Version: 2026-03-10) and require proper authentication scopes, such as fine-grained personal access tokens or GitHub App installation tokens with repository-level permissions. By exposing these new endpoints, GitHub is targeting development teams looking to automate quality assurance processes at scale, particularly those managing large repositories or multi-repository projects.

These updates build on a series of enhancements to GitHub Code Quality in recent months, including organization-level dashboards, quality scoring, and enforcement features introduced in April and June 2026. As GitHub positions Code Quality as a central tool for developer productivity, these API updates could drive further adoption by easing integration challenges.

For developers and enterprises, the timing is critical. With the general availability date set for next month, teams have a narrow window to test these APIs without incurring additional costs. Organizations relying on GitHub Actions workflows for CI/CD stand to benefit the most, as direct API support can streamline quality checks and reduce manual intervention.

More information about the public preview and how to use the new endpoints can be found in GitHub’s official changelog.

Image source: Shutterstock