Enabling alerts for vulnerable dependencies on GitHub Enterprise Server

You can connect your GitHub Enterprise Server instance to GitHub Enterprise Cloud and enable Dependabot alerts for vulnerable dependencies in repositories in your instance.

Site administrators for GitHub Enterprise Server who are also owners of the connected GitHub Enterprise Cloud organization or enterprise account can enable Dependabot alerts for vulnerable dependencies on GitHub Enterprise Server.

In this article

Did this doc help you?

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.

About alerts for vulnerable dependencies on GitHub Enterprise Server

We add vulnerabilities to the GitHub Advisory Database from the following sources:

You can connect your GitHub Enterprise Server instance to GitHub.com, then sync vulnerability data to your instance and generate Dependabot alerts in repositories with a vulnerable dependency.

After connecting your GitHub Enterprise Server instance to GitHub.com and enabling Dependabot alerts for vulnerable dependencies, vulnerability data is synced from GitHub.com to your instance once every hour. You can also choose to manually sync vulnerability data at any time. No code or information about code from your GitHub Enterprise Server instance is uploaded to GitHub.com.

When your GitHub Enterprise Server instance receives information about a vulnerability, it will identify repositories in your instance that use the affected version of the dependency and generate Dependabot alerts. You can customize how you receive Dependabot alerts. For more information, see "Configuring notifications for vulnerable dependencies."

Enabling Dependabot alerts for vulnerable dependencies on GitHub Enterprise Server

Before enabling Dependabot alerts for vulnerable dependencies on your GitHub Enterprise Server instance, you must connect your GitHub Enterprise Server instance to GitHub.com. For more information, see "Connecting GitHub Enterprise Server to GitHub Enterprise Cloud."

We recommend configuring Dependabot alerts without notifications for the first few days to avoid an overload of emails. After a few days, you can enable notifications to receive Dependabot alerts as usual.

  1. Sign in to your GitHub Enterprise Server instance at http(s)://HOSTNAME/login.

  2. In the administrative shell, enable the Dependabot alerts for vulnerable dependencies on your GitHub Enterprise Server instance:

    $ ghe-dep-graph-enable

    Note: For more information about enabling access to the administrative shell via SSH, see "Accessing the administrative shell (SSH)."

  3. Return to GitHub Enterprise Server.

  4. From a GitHub Enterprise Server administrative account, click in the upper-right corner of any page.

    Rocketship icon for accessing site admin settings

  5. In the left sidebar, click Enterprise overview.

    Enterprise overview tab in the Site admin settings

  6. In the enterprise account sidebar, click Settings.

    Settings tab in the enterprise account sidebar

  7. In the left sidebar, click GitHub Connect.

    GitHub Connect tab in the business account settings sidebar

  8. Under "Repositories can be scanned for vulnerabilities", use the drop-down menu and select Enabled without notifications. Optionally, to enable alerts with notifications, select Enabled with notifications.

    Drop-down menu to enable scanning repositories for vulnerabilities

Viewing vulnerable dependencies on GitHub Enterprise Server

You can view all vulnerabilities in your GitHub Enterprise Server instance and manually sync vulnerability data from GitHub.com to update the list.

  1. From a GitHub Enterprise Server administrative account, click in the upper-right corner of any page.
    Rocketship icon for accessing site admin settings
  2. In the left sidebar, click Vulnerabilities.
    Vulnerabilities tab in the site admin sidebar
  3. To sync vulnerability data, click Sync Vulnerabilities now.
    Sync vulnerabilities now button

Did this doc help you?

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.