GitHub adds Code Quality license estimates before July 20 paid launch

GitHub has added a license-cost estimate for GitHub Code Quality, giving enterprise and team administrators a clearer view of what the service may cost before it moves from public preview to general availability.

The change, announced in GitHub's July 13 changelog, shows the number of active committers on repositories using Code Quality across an enterprise. GitHub says the estimate is intended to help customers understand the per-committer licensing impact before the product becomes paid on July 20, 2026.

What administrators can see

The estimate appears in the billing entity's Billing and licensing area under Licensing. A Code Quality card shows consumed licenses and an estimated monthly payment, turning what could otherwise be an abstract preview feature into a more concrete budgeting signal for organizations that have enabled Code Quality across multiple repositories.

GitHub also spelled out important limits on the estimate. It covers only the per-committer license cost. It does not include GitHub Actions minutes consumed by CodeQL analysis, nor does it include usage-based charges for AI-powered features such as GitHub Copilot Autofix. The estimate is also based on standard list pricing, so negotiated discounts or account-specific terms may not be reflected.

Pricing and availability

GitHub says Code Quality remains free during the public preview, but the product is scheduled to become generally available on July 20, 2026. At that point, GitHub lists pricing at $10 per active committer per month.

The feature is available for GitHub Enterprise Cloud and GitHub Team customers, but not for GitHub Enterprise Server. That distinction matters for organizations running self-managed GitHub deployments, which will not be able to use the hosted Code Quality service in the same way as cloud customers.

For engineering leaders, the update is less about a new scanner than about procurement readiness. Code-quality and application-security tooling can spread quickly once enabled at the organization level, and per-committer pricing can make costs rise with developer participation rather than with a fixed repository count. Surfacing the estimate before billing begins gives administrators a short window to review adoption, compare the expected charge with the security and maintenance benefits, and decide where Code Quality should stay enabled.

Sources

• github.blog

Cover photo by Daniil Komov on Pexels, used under the Pexels License.