Direct answer
Preview teams should check enabled scope before more paid scans run
GitHub Code Quality became a paid generally available product on July 20, 2026. If your organization enabled it during preview, GitHub says the configuration continues without migration and billing begins automatically. The base list price is $10 per active committer each month, while AI-powered analysis and GitHub Actions usage are separate charges. Check the current consumed-license estimate, confirm which repositories are enabled, then keep, narrow, or disable the product based on the value those repositories receive.
Decision first
Keep it, scope it, or disable it
Coverage is intentional
Keep the current scope when the enabled repositories are active, the findings influence reviews or quality gates, and the team accepts all three cost layers.
Value differs by repository
Narrow the enabled set when only production, customer-facing, regulated, or actively maintained repositories justify ongoing analysis and billing.
The preview is no longer justified
Disable Code Quality when the team did not approve the paid transition or cannot connect its findings to an owned engineering workflow. GitHub says disabling stops future scans and associated billing.
What changed July 20
General availability turned a preview configuration into a live cost decision
GitHub says more than 10,000 enterprises used the public preview. That number shows broad preview adoption, but it is not a billable-customer count: GitHub does not disclose how many preview organizations remain enabled, how many active committers they have, or what account-specific discounts may apply.
The operational consequence is narrower and more important. Existing preview configurations continue without migration or reconfiguration. A team that treated the feature as an experiment now needs an explicit owner for repository scope, license estimates, AI-credit use, Actions consumption, and the keep-or-disable decision.
Reproducible calculation
GitHub Code Quality base-license cost floors
At GitHub’s published list price, the base monthly floor is active committers x $10. The annualized floor below multiplies that monthly amount by 12. These are planning scenarios, not quotes.
Boundary: These figures use standard list price only. They exclude GitHub AI Credits, GitHub Actions minutes, taxes, negotiated discounts, enterprise contracts, and changes in the rolling 90-day active-committer population.
The full cost map
Budget for three separate billing layers
Active-committer licenses
GitHub charges $10 per active committer per month at standard list price. A person is active when a commit from that person is pushed to an enabled repository within the previous 90 days.
GitHub AI Credits
AI-assisted detection and Copilot Autofix consume GitHub AI Credits. GitHub currently defines one AI credit as $0.01, so usage depends on which AI features the team invokes and how often.
GitHub Actions compute
Deterministic CodeQL analysis uses GitHub Actions minutes when it runs on GitHub-hosted runners. Self-hosted runner economics and existing plan allowances can change the practical total.
Do not multiply headcount by $10 and call the estimate complete. Start with the current consumed-license estimate in GitHub billing, then layer in observed AI-credit and Actions usage. GitHub notes that the license estimate itself has limitations, so finance and engineering should treat it as an operating signal rather than a fixed invoice forecast.
Who should act now
Organizations that enabled Code Quality during preview and have not explicitly approved its paid scope should review it immediately because GitHub says those configurations continue and billing begins automatically.
GitHub Team and Enterprise Cloud customers considering enablement should estimate the rolling active-committer population and the likely AI and Actions usage before turning it on broadly.
GitHub Enterprise Server customers cannot use GitHub Code Quality at general-availability launch. This article does not imply a self-hosted product path exists.
GitHub counts a person once across the organization or enterprise even when that person contributes to multiple enabled repositories. GitHub App bots are excluded, but ordinary automation identities or service accounts should be checked against GitHub’s exact billing definition instead of assumed to be free.
15-minute control check
What engineering and finance should verify today
- 1
Name an owner
Assign one person to own the paid-product decision, repository scope, and recheck date. A preview configuration without an owner is the risky state.
- 2
Open the consumed-license estimate
Record GitHub’s current estimate and the billing entity that owns it. Compare the estimate with the engineers who actually pushed to enabled repositories during the rolling 90-day window.
- 3
List enabled repositories
Separate repositories that actively use findings or quality gates from dormant, archived, experimental, or low-value coverage. Scope should follow a documented engineering need.
- 4
Measure the variable layers
Review AI-credit and GitHub Actions consumption. Record whether analyses run on GitHub-hosted or self-hosted runners and which workflows trigger the use.
- 5
Record the decision
Keep, narrow, or disable the product, then set a 30-day review against findings used, pull requests influenced, false-positive burden, and total cost.
What is confirmed and what remains account-specific
General availability, supported cloud plans, $10 list pricing, the rolling 90-day committer rule, separate AI and Actions costs, preview continuity, and the disablement effect are documented.
The useful decision is not whether the product is generally available. It is whether each enabled repository produces enough operational value to justify the base and variable costs.
The exact bill depends on the consumed-license population, AI usage, Actions setup, allowances, discounts, contracts, taxes, and scope changes. The examples here are not account quotes.
TPTK will update this permanent URL if GitHub changes list pricing, active-committer rules, AI-credit rates, Actions billing, plan eligibility, repository controls, or Enterprise Server availability.
GitHub Code Quality billing FAQ
How much does GitHub Code Quality cost?
GitHub lists Code Quality at $10 per active committer per month. AI-powered detection and Copilot Autofix use GitHub AI Credits, and deterministic CodeQL analysis can consume GitHub Actions minutes, so the license amount is only the base layer.
Who counts as an active committer?
GitHub defines an active committer as a person whose commit is pushed to an enabled repository within the preceding 90 days. A person is counted once across the organization or enterprise, and GitHub App bots are excluded.
Does GitHub Code Quality require GitHub Copilot?
No. GitHub describes Code Quality as a standalone paid product. Some AI-assisted capabilities consume GitHub AI Credits, but the product is not presented as requiring a Copilot subscription.
How do I stop future GitHub Code Quality charges?
Use GitHub’s documented organization or repository controls to disable Code Quality. GitHub says disabling it stops future scans and associated billing; verify access roles and the resulting repository state in your own account.
Update log
July 20, 2026 at 11:40 AM PDT: Initial publication. GitHub’s launch notice, billing definition, product controls, disable path, license-floor calculations, visual package, links, and schema were verified.
Sources
- GitHub Changelog: GitHub Code Quality is now generally available. Published July 20, 2026; accessed July 20, 2026.
- GitHub Docs: GitHub Code Quality billing. Accessed July 20, 2026.
- GitHub Docs: About GitHub Code Quality. Accessed July 20, 2026.
- GitHub Docs: Disabling GitHub Code Quality. Accessed July 20, 2026.
All central factual claims use GitHub’s announcement and documentation. TPTK’s monthly examples multiply the published active-committer list price; the annualized examples multiply that monthly result by 12.
Editorial note: This authority-only billing briefing contains no affiliate links, Amazon bounty module, or unsupported deal claim. Material corrections and source changes will be recorded in the update log.