GitHub has added a CSV export for Code Quality license usage, accessible from the Billing and licensing page of an organization or enterprise. The file lists every active committer who is currently consuming a license, the repositories they touched in the past 90 days, and whether the committer is unique to a single repository or organization. Practitioners can use this data to verify that the number of licenses billed matches actual usage and to identify opportunities to disable Code Quality on low‑impact contributors.
How to Obtain the CSV
- Navigate to the Billing and licensing section of your GitHub organization or enterprise.
- Select the Licensing tab.
- Locate the Code Quality card and click the download button to receive the CSV file.
The feature is available for GitHub Team and GitHub Enterprise Cloud customers.
Operational Implications
Having a machine‑readable list of license consumers enables automated reconciliation processes. Teams can script periodic imports of the CSV into internal asset‑tracking systems, compare against HR or IAM records, and flag mismatches before the next billing cycle. The report’s 90‑day commit window helps focus on recent activity, reducing noise from dormant accounts.
Potential Impact on Security and Governance
While the CSV itself does not expose code or secrets, it reveals which identities are tied to a paid security‑related feature. Auditors may request this evidence to confirm that only authorized developers have access to Code Quality analysis. Organizations should treat the export as a sensitive artifact, store it with the same controls applied to other licensing or billing data, and limit access to personnel responsible for cost management or compliance.
Related CloudNinjas coverage: DevOps.
What This Means For Practitioners
Export the CSV on a regular cadence, ingest it into your existing license‑tracking workflow, and cross‑reference the committer list with your internal developer directory. Look for contributors who appear on the list but have minimal or no recent commits; consider disabling Code Quality for those accounts to free up seats. Keep an eye on any changes to the export format or availability in future GitHub releases, and adjust your automation accordingly.