Skip to main content

Configuring notifications for Dependabot alerts

Optimize how you receive notifications about Dependabot alerts.

About notifications for Dependabot alerts

When Dependabot detects vulnerable dependencies in your repositories, we generate a Dependabot alert and display it on the Security tab for the repository. GitHub Enterprise Server notifies the maintainers of affected repositories about the new alert according to their notification preferences.

By default, if your enterprise owner has configured email for notifications on your enterprise, you will receive Dependabot alerts by email.

Enterprise owners can also enable Dependabot alerts without notifications. For more information, see "Enabling Dependabot for your enterprise."

Configuring notifications for Dependabot alerts

When a new Dependabot alert is detected, GitHub Enterprise Server notifies all users with access to Dependabot alerts for the repository according to their notification preferences. You will receive alerts if you are watching the repository, have enabled notifications for security alerts or for all the activity on the repository, and are not ignoring the repository. For more information, see "Configuring notifications."

You can configure notification settings for yourself or your organization from the Manage notifications drop-down shown at the top of each page. For more information, see "Configuring notifications."

Puedes elegir el método de entrega de las notificaciones, así como la frecuencia en las que se te envían. By default, if your enterprise owner has configured email for notifications on your instance, you will receive Dependabot alerts:

  • in your inbox, as web notifications. A web notification is sent when Dependabot is enabled for a repository, when a new manifest file is committed to the repository, and when a new vulnerability with a critical or high severity is found (On GitHub option).

  • by email, an email is sent when Dependabot is enabled for a repository, when a new manifest file is committed to the repository, and when a new vulnerability with a critical or high severity is found (Email option).

  • in the user interface, a warning is shown in your repository's file and code views if there are any insecure dependencies (UI alerts option).

  • on the command line, warnings are displayed as callbacks when you push to repositories with any insecure dependencies (CLI option).

  • on GitHub Mobile, as web notifications. For more information, see "Enabling push notifications with GitHub Mobile."

Note: The email and web/GitHub Mobile notifications are:

  • per repository when Dependabot is enabled on the repository, or when a new manifest file is committed to the repository.

  • per organization when a new vulnerability is discovered.

You can customize the way you are notified about Dependabot alerts. For example, you can receive a weekly digest email summarizing alerts for up to 10 of your repositories using the Email a digest summary of vulnerabilities and Weekly security email digest options.

Screenshot of the Dependabot alerts options

Note: You can filter your notifications on GitHub to show Dependabot alerts. For more information, see "Managing notifications from your inbox."

Las notificaciones por correo electrónico para Dependabot alerts que afectan a uno o más repositorios incluyen el campo de encabezado X-GitHub-Severity. Puede usar el valor del campo de encabezado X-GitHub-Severity para filtrar las notificaciones por correo electrónico de Dependabot alerts. For more information, see "Configuring notifications."

How to reduce the noise from notifications for Dependabot alerts

If you are concerned about receiving too many notifications for Dependabot alerts, we recommend you opt into the weekly email digest, or turn off notifications while keeping Dependabot alerts enabled. You can still navigate to see your Dependabot alerts in your repository's Security tab. For more information, see "Viewing and updating Dependabot alerts."

Further reading