Skip to main content

Enabling Dependabot for your enterprise

You can allow users of your GitHub Enterprise Server instance to find and fix vulnerabilities in code dependencies by enabling Dependabot alerts and Dependabot updates.

Who can use this feature

Enterprise owners can enable Dependabot.

About Dependabot for GitHub Enterprise Server

Dependabot helps users of your GitHub Enterprise Server instance find and fix vulnerabilities in their dependencies. You can enable Dependabot alerts to notify users about vulnerable dependencies and Dependabot updates to fix the vulnerabilities and keep dependencies updated to the latest version.

Dependabot is just one of many features available to harden supply chain security for your GitHub Enterprise Server instance. For more information about the other features, see "About supply chain security for your enterprise."

About Dependabot alerts

With Dependabot alerts, GitHub identifies insecure dependencies in repositories and creates alerts on your GitHub Enterprise Server instance, using data from the GitHub Advisory Database and the dependency graph service.

Agregamos asesorías a la GitHub Advisory Database desde los siguientes orígenes:

Si conoce otra base de datos de la que deberíamos importar avisos, háganoslo saber si abre un problema en https://github.com/github/advisory-database.

After you enable Dependabot alerts for your enterprise, vulnerability data is synced from the GitHub Advisory Database to your instance once every hour. Only GitHub-reviewed advisories are synchronized. Para obtener más información, consulta "Exploración de avisos de seguridad en GitHub Advisory Database".

You can also choose to manually sync vulnerability data at any time. For more information, see "Viewing the vulnerability data for your enterprise."

Note: When you enable Dependabot alerts, 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 identifies repositories in your GitHub Enterprise Server instance that use the affected version of the dependency and generates Dependabot alerts. You can choose whether or not to notify users automatically about new Dependabot alerts.

For repositories with Dependabot alerts enabled, scanning is triggered on any push to the default branch that contains a manifest file or lock file. Additionally, when a new vulnerability record is added to your GitHub Enterprise Server instance, GitHub Enterprise Server scans all existing repositories on your GitHub Enterprise Server instance and generates alerts for any repository that is vulnerable. For more information, see "About Dependabot alerts."

About Dependabot updates

After you enable Dependabot alerts, you can choose to enable Dependabot updates. When Dependabot updates are enabled for your GitHub Enterprise Server instance, users can configure repositories so that their dependencies are updated and kept secure automatically.

Note: Dependabot updates on GitHub Enterprise Server requires GitHub Actions with self-hosted runners.

By default, GitHub Actions runners used by Dependabot need access to the internet, to download updated packages from upstream package managers. For Dependabot updates powered by GitHub Connect, internet access provides your runners with a token that allows access to dependencies and advisories hosted on GitHub.com.

With Dependabot updates, GitHub automatically creates pull requests to update dependencies in two ways.

  • Dependabot version updates: Users add a Dependabot configuration file to the repository to enable Dependabot to create pull requests when a new version of a tracked dependency is released. For more information, see "About Dependabot version updates."
  • Dependabot security updates: Users toggle a repository setting to enable Dependabot to create pull requests when GitHub detects a vulnerability in one of the dependencies of the dependency graph for the repository. For more information, see "About Dependabot alerts" and "About Dependabot security updates."

Enabling Dependabot alerts

Before you can enable Dependabot alerts:

  1. En la esquina superior derecha de GitHub Enterprise Server, haga clic en la foto de perfil y luego en Configuración de empresa. "Configuración de empresa" en el menú desplegable de la foto de perfil de GitHub Enterprise Server

  2. En la barra lateral de la cuenta empresarial, haga clic en GitHub Connect . Pestaña GitHub Connect en la barra lateral de la cuenta empresarial

  3. Under "Dependabot", to the right of "Users can receive vulnerability alerts for open source code dependencies", select the dropdown menu and click Enabled without notifications. Optionally, to enable alerts with notifications, click Enabled with notifications.

    Screenshot of the dropdown menu to enable scanning repositories for vulnerabilities

    Tip: 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.

Enabling Dependabot updates

After you enable Dependabot alerts for your enterprise, you can enable Dependabot updates.

Antes de habilitar Dependabot updates, debes configurar your GitHub Enterprise Server instance para que use GitHub Actions con ejecutores autohospedados. For more information, see "Getting started with GitHub Actions for GitHub Enterprise Server."

Dependabot updates are not supported on GitHub Enterprise Server if your enterprise uses clustering.

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

  2. Desde una cuenta administrativa de GitHub Enterprise Server, en la esquina superior derecha de cualquier página, haz clic en .

    Captura de pantalla del icono de cohete para acceder a los ajustes administrativos

  3. Si todavía no está en la página "Administrador del sitio", en la esquina superior izquierda, haga clic en Administrador del sitio.

    Captura de pantalla del vínculo "Administrador del sitio"

  4. En la barra lateral de la izquierda, haga clic en Consola de administración . Pestaña Consola de administración en la barra lateral de la izquierda

  5. En la barra lateral izquierda, haga clic en Security (Seguridad). Barra lateral de seguridad

  6. Under "Security", select Dependabot security updates.

    Screenshot of the checkbox to enable or disable Dependabot security updates

  7. En la barra lateral de la izquierda, haga clic en Guardar configuración.

    Captura de pantalla del botón para guardar los ajustes en la Consola de administración

    Nota: Al guardar la configuración en la Consola de administración se restablecen los servicios de sistema, lo que podría generar un tiempo de inactividad visible para el usuario.

  8. Espera que se complete la fase de configuración.

    Configurar tu instancia

  9. Click Visit your instance.

  10. Configure dedicated self-hosted runners to create the pull requests that will update dependencies. This is required because the workflows use a specific runner label. For more information, see "Managing self-hosted runners for Dependabot updates on your enterprise."

  11. En la esquina superior derecha de GitHub Enterprise Server, haga clic en la foto de perfil y luego en Configuración de empresa. "Configuración de empresa" en el menú desplegable de la foto de perfil de GitHub Enterprise Server

  12. En la barra lateral de la cuenta empresarial, haga clic en GitHub Connect . Pestaña GitHub Connect en la barra lateral de la cuenta empresarial

  13. Under "Dependabot", to the right of "Users can easily upgrade to non-vulnerable open source code dependencies", click Enable.

    Screenshot of the dropdown menu to enable updating vulnerable dependencies

When you enable Dependabot alerts, you should consider also setting up GitHub Actions for Dependabot security updates. This feature allows developers to fix vulnerabilities in their dependencies. For more information, see "Managing self-hosted runners for Dependabot updates on your enterprise."

If you need enhanced security, we recommend configuring Dependabot to use private registries. For more information, see "Managing encrypted secrets for Dependabot."