Frecuentemente publicamos actualizaciones de nuestra documentación. Es posible que la traducción de esta página esté en curso. Para conocer la información más actual, visita la documentación en inglés. Si existe un problema con las traducciones en esta página, por favor infórmanos.

About alerts for vulnerable dependencies

GitHub Enterprise sends Alertas del Dependabot de GitHub when we detect vulnerabilities affecting your repository.

En este artículo

About vulnerable dependencies

Una vulnerabilidad es un problema en el código de un proyecto que se puede aprovechar para dañar la confidencialidad, la integridad o la disponibilidad del proyecto o de otros proyectos que usan su código. Las vulnerabilidades varían en tipo, severidad y método de ataque.

When your code depends on a package that has a security vulnerability, this vulnerable dependency can cause a range of problems for your project or the people who use it.

Detection of vulnerable dependencies

Dependabot de GitHub detects vulnerable dependencies and sends alerts when:

For a list of the ecosystems that GitHub Enterprise can detect vulnerabilities and dependencies for, see "Supported package ecosystems."

Note: It is important to keep your manifest and lock files up to date. If the dependency graph doesn't accurately reflect your current dependencies and versions, then you could miss alerts for vulnerable dependencies that you use. You may also get alerts for dependencies that you no longer use.

Dependabot de GitHub alerts for vulnerable dependencies

Your site administrator must enable Tu administrador de sitio debe habilitar las alertas de seguridad para las dependencias vulnerables de tu instancia de servidor de GitHub Enterprise para que puedas utilizar esta característica. Para obtener más información, consulta "Habilitar alertas de seguridad para dependencias vulnerables en el Servidor de GitHub Enterprise".

When GitHub Enterprise identifies a vulnerable dependency, we send a alert to the maintainers of affected repositories with details of the vulnerability, a link to the affected file in the project, and information about a fixed version.

Note: GitHub Enterprise's security features do not claim to catch all vulnerabilities. Though we are always trying to update our vulnerability database and alert you with our most up-to-date information, we will not be able to catch everything or alert you to known vulnerabilities within a guaranteed time frame. These features are not substitutes for human review of each dependency for potential vulnerabilities or any other issues, and we recommend consulting with a security service or conducting a thorough vulnerability review when necessary.

Access to alerts

You can see all of the alerts that affect a particular project in the repository's dependency graph.

We send alerts to people with admin permissions in the affected repositories by default. GitHub Enterprise never publicly discloses identified vulnerabilities for any repository.

Configuring notifications for Alertas del Dependabot de GitHub

By default, if your site administrator has configured email for notifications on your instance, you will receive Alertas del Dependabot de GitHub by email. You can also choose to receive Alertas del Dependabot de GitHub in a weekly email summarizing alerts for up to 10 of your repositories, in your web notifications, or in the GitHub Enterprise user interface. For more information, see "Configuring notifications."

Site administrators can also enable Alertas del Dependabot de GitHub without notifications. For more information, see "Enabling alerts for vulnerable dependencies on Servidor de GitHub Enterprise."

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

¿Te ayudó este documento?

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

O, learn how to contribute.