GitHub has many features that help you improve and maintain the quality of your code. Some of these are included in all plans, for example: dependency graph and Dependabot alerts. Other security features require a license for GitHub Advanced Security to run on repositories apart from public repositories on GitHub.com. (That is, private and internal repositories on GitHub.com, and all repositories on GitHub Enterprise Server.)
For an overview of all security features, see "About securing your repository." For information about permission requirements for actions related to security features, see "Repository permission levels for an organization."
A GitHub Advanced Security license provides the following additional features:
Code scanning - Search for potential security vulnerabilities and coding errors in your code. For more information, see "About code scanning."
Secret scanning - Detect secrets, for example keys and tokens, that have been checked into the repository. For more information, see "About secret scanning."
Dependency review - Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "Reviewing dependency changes in a pull request."
For information about Advanced Security features that are in development, see "GitHub public roadmap."
Each license for GitHub Advanced Security specifies a maximum number of committers whose work can use these features. A committer is someone who authored at least one commit that was pushed to the repository in the last 90 days. Each committer is counted once, no matter how many repositories they contribute to.
When you enable GitHub Advanced Security, GitHub shows how many extra committers this will add and prompts for confirmation. If you disable access to GitHub Advanced Security, you can see how many seats this will free before you confirm the change. This makes it easy to see the impact of your changes on the use of your license.
For public repositories on GitHub.com, these features are permanently on and are only disabled if you change the visibility of the project so that the code is no longer public.
For other repositories, once you have a license for your organization or enterprise, you can enable and disable these features at the organization or repository level. For more information, see "Managing security and analysis settings for your organization" and "Managing security and analysis settings for your repository."
If you have an enterprise account, license use for the enterprise is shown on your billing page. For more information, see "Managing use of Advanced Security for organizations in your enterprise account."
For information about purchasing a license for GitHub Advanced Security, contact GitHub's Sales team.