Managing security and analysis settings for your repository

You can control features that secure and analyze the code in your project on GitHub.

People with admin permissions to a repository can manage security and analysis settings for the repository.

In this article

Enabling or disabling security and analysis features for public repositories

You can manage a subset of security and analysis features for public repositories. Other features are permanently enabled, including dependency graph and secret scanning.

  1. On GitHub, navigate to the main page of the repository.
  2. Under your repository name, click Settings. Repository settings button
  3. In the left sidebar, click Security & analysis. "Security & analysis" tab in repository settings
  4. Under "Configure security and analysis features", to the right of the feature, click Disable or Enable. "Enable" or "Disable" button for "Configure security and analysis" features in a public repository

Enabling or disabling security and analysis features for private repositories

You can manage the security and analysis features for your private or internal repository. If your organization belongs to an enterprise with a license for GitHub Advanced Security then extra options are available. For more information, see "About GitHub Advanced Security."

If you enable security and analysis features, GitHub performs read-only analysis on your repository. For more information, see "About GitHub's use of your data."

  1. On GitHub, navigate to the main page of the repository.

  2. Under your repository name, click Settings. Repository settings button

  3. In the left sidebar, click Security & analysis. "Security & analysis" tab in repository settings

  4. Under "Configure security and analysis features", to the right of the feature, click Disable or Enable. The control for "GitHub Advanced Security" is disabled if your enterprise has no available licenses for Advanced Security. "Enable" or "Disable" button for "Configure security and analysis" features

    Note: If you disable GitHub Advanced Security, dependency review, secret scanning and code scanning are disabled. Any workflows, SARIF uploads, or API calls for code scanning will fail.

Granting access to security alerts

After you enable Dependabot or secret scanning alerts for a repository in an organization, organization owners and repository administrators can view the alerts by default. You can give additional teams and people access to the alerts for a repository.

Organization owners and repository administrators can only grant access to view security alerts, such as secret scanning alerts, to people or teams who have write access to the repo.

  1. On GitHub, navigate to the main page of the repository.

  2. Under your repository name, click Settings. Repository settings button

  3. In the left sidebar, click Security & analysis. "Security & analysis" tab in repository settings

  4. Under "Access to alerts", in the search field, start typing the name of the person or team you'd like to find, then click a name in the list of matches.

    Search field for granting people or teams access to security alerts

  5. Click Save changes.

    "Save changes" button for changes to security alert settings

Removing access to security alerts

  1. On GitHub, navigate to the main page of the repository.
  2. Under your repository name, click Settings. Repository settings button
  3. In the left sidebar, click Security & analysis. "Security & analysis" tab in repository settings
  4. Under "Access to alerts", to the right of the person or team whose access you'd like to remove, click ."x" button to remove someone's access to security alerts for your repository

Further reading

Did this doc help you?Privacy policy

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Or, learn how to contribute.