Not enough GitHub Advanced Security licenses

You need available GHAS licenses to enable GHAS features on a private repository.

Who can use this feature?

Organization owners and security managers can manage security configurations and global settings for an organization.

Note: Security configurations and global settings are in beta and subject to change.

You must have an available GitHub Advanced Security (GHAS) license for each unique active committer to enable GHAS features on a private repository. To learn about GHAS licensing, as well as unique and active committers, see "About billing for GitHub Advanced Security."

If you try to apply a security configuration with GHAS features to your repositories and don't have enough GHAS licenses, the configuration will only be successfully applied to public repositories. For private repositories, only free security features will be enabled due to the license limitation, resulting in the following outcomes:

  • Free security features enabled in the configuration will be enabled for all private repositories.
  • GHAS features will not be enabled for any private repositories.
  • The security configuration will not be applied to any private repositories, since only some features from the configuration are enabled.

For more information on managing GHAS licenses for your organization, see "Managing your GitHub Advanced Security license usage."