Skip to main content
Мы публикуем частые обновления нашей документации, и перевод этой страницы, возможно, еще выполняется. Актуальные сведения см. в документации на английском языке.

Сведения о GitHub Advanced Security

GitHub обеспечивает клиентам доступ к дополнительным функциям безопасности в рамках лицензии Advanced Security Кроме того, эти функции включены для общедоступных репозиториев в

GitHub Advanced Security доступен для корпоративных учетных записей в GitHub Enterprise Cloud и GitHub Enterprise Server. Некоторые функции GitHub Advanced Security также доступны для общедоступных репозиториев для Дополнительные сведения см. в разделе Продукты GitHub.

About GitHub Advanced Security

GitHub has many features that help you improve and maintain the quality of your code. Some of these are included in all plans, such as dependency graph and Dependabot alerts. Other security features require a GitHub Advanced Security license to run on repositories apart from public repositories on

For information about buying a license for GitHub Advanced Security, see "Signing up for GitHub Advanced Security."

About Advanced Security features

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. If push protection is enabled, also detects secrets when they are pushed to your repository. For more information, see "About secret scanning" and "Protecting pushes with 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 "About dependency review."

The table below summarizes the availability of GitHub Advanced Security features for public and private repositories.

Public repositoryPrivate repository
without Advanced Security
Private repository
with Advanced Security
Code scanning
Secret scanning
Dependency review

For information about Advanced Security features that are in development, see "GitHub public roadmap." For an overview of all security features, see "GitHub security features."

GitHub Advanced Security features are enabled for all public repositories on Organizations that use GitHub Enterprise Cloud with Advanced Security can additionally enable these features for private and internal repositories.

Deploying GitHub Advanced Security in your enterprise

To learn about what you need to know to plan your GitHub Advanced Security deployment at a high level and to review the rollout phases we recommended, see "Adopting GitHub Advanced Security at scale."

Enabling Advanced Security features

For public repositories these features are permanently on and can only be 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 enterprise account, 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 entire enterprise is shown on your enterprise license page. For more information, see "Viewing your GitHub Advanced Security usage."

About starter workflows for Advanced Security

Note: Starter workflows for Advanced Security have been consolidated in a "Security" category in the Actions tab of a repository. This new configuration is currently in beta and subject to change.

GitHub Enterprise Cloud provides starter workflows for security features such as code scanning. You can use these suggested workflows to construct your code scanning workflows, instead of starting from scratch.

For more information on starter workflows, see "Configuring code scanning for a repository" and "Using starter workflows."

Further reading