Skip to main content
In this lesson you’ll learn how to audit adoption and optimize license usage for your enterprise GitHub account. The goal is to identify unused or underused Advanced Security seats (CodeQL/code scanning and Secret Protection) and reclaim them for active contributors, reducing monthly costs without interrupting developer workflows.

Where to find billing and license details

As an enterprise administrator, view billing and licensing information from the Enterprise (or Organization) settings in GitHub. The Licensing tab displays:
  • Total licenses consumed and any recent changes (for example: a count dropping from three to two after removing a user).
  • An estimated monthly cost for consumed licenses.
  • Advanced Security usage summarized separately (Code Security and Secret Protection).
These high-level numbers tell you how many seats you are paying for, but not who actually used those features or when. To make informed decisions, download and inspect the CSV reports that GitHub provides.

Advanced Security: what to audit

Advanced Security usage is split into two reports that you should review:
  • Secret Protection — lists users who triggered or used Secret Scanning / Secret Protection, including the organization and repository where it occurred and the last-used timestamp.
  • Code Security — lists users who used CodeQL/code scanning features, with repository context and last-used timestamp.
Use these reports together with the Enterprise CSV to correlate assigned licenses with actual activity.

Downloading and analyzing the CSV reports

  1. From the Enterprise Licensing tab, download the Enterprise Cloud CSV report. This includes all users in the enterprise and fields such as:
    • Enterprise role
    • Organization-level role
    • Two-factor authentication requirement date
    • Whether Advanced Security features are assigned (Code Security / Secret Protection)
  2. Download the Advanced Security reports:
    • Secret Protection report
    • Code Security report
  3. Open each CSV in a spreadsheet application (Excel, Google Sheets, etc.) and inspect the following fields to assess usage and recency:
    • last_pushed or last pushed date (committer activity)
    • Advanced Security last-used timestamps (from Code Security and Secret Protection reports)
    • Organization and repository where the feature was used
Below is an example of a CSV extract showing active committers and last push metadata.
A screenshot of an Excel worksheet showing a table of active committers with columns for User login, Organization/repository, Last pushed date, and Last pushed email. It lists three rows for "alice-admin-kk" with repositories (game-devstudio/app-backend, .github, ghas-guardrail-demo), dates in August 2026, and the email alice.gh900+ADMIN@gmail.com.

Quick checklist when inspecting CSV data

  • Confirm the last pushed dates for users assigned Advanced Security licenses.
  • Cross-reference the Code Security and Secret Protection last-used timestamps.
  • Note the repository and organization context to verify whether the activity is relevant to the license assignment.

Report summary

  1. Download the Enterprise Cloud CSV to get the list of assigned licenses and user roles.
  2. Download the Advanced Security reports (Secret Protection and Code Security) to obtain last-used timestamps and repository context.
  3. Cross-reference last pushed (or other commit activity) with Advanced Security last-used dates.
  4. Identify users with licenses who haven’t pushed or used Advanced Security features recently.
  5. Verify inactivity with team leads, onboarding/offboarding logs, or by contacting the user directly.
  6. Reclaim licenses from confirmed inactive users and reassign them to active contributors who need Advanced Security features.
Always correlate “last pushed” or “last used” dates with your team’s onboarding/offboarding records and direct confirmations before removing licenses. Notify the user or their manager to confirm inactivity to avoid disrupting active work.
By following this process you can reduce wasted spend on unused Advanced Security seats while ensuring active developers retain the tools they need.

Watch Video