Managing alerts from secret scanning

You can view and close alerts for secrets checked in to your repository.

Secret scanning is available in public repositories, and in private repositories owned by organizations with an Advanced Security license. For more information, see "GitHub's products."

In this article

Note: Secret scanning for private repositories is currently in beta and subject to change.

Managing alerts

  1. On GitHub, navigate to the main page of the repository.
  2. Under your repository name, click Security.
    Security tab
  3. In the left sidebar, click Detected secrets.
    "Detected secrets" tab
  4. Under "Secret scanning" click the alert you want to view.
    List of alerts from secret scanning
  5. Optionally, use the "Resolve" drop-down menu and click a reason for resolving an alert.
    Drop-down menu for resolving an alert from secret scanning

Securing compromised secrets

Once a secret has been committed to a repository, you should consider the secret compromised. GitHub recommends the following actions for compromised secrets:

  • For a compromised GitHub personal access token, delete the compromised token, create a new token, and update any services that use the old token. For more information, see "Creating a personal access token for the command line."
  • For all other secrets, first verify that the secret committed to GitHub is valid. If so, create a new secret, update any services that use the old secret, and then delete the old secret.

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.