About alerts for vulnerable dependencies

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

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 Alertas del Dependabot de GitHub 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 generate a Dependabot de GitHub alert and display it on the Security tab for the repository. The alert includes a link to the affected file in the project, and information about a fixed version. GitHub Enterprise also notifies the maintainers of affected repositories about the new alert according to their notification preferences. For more information, see "Configuring notifications for vulnerable dependencies."

Note: GitHub Enterprise's security features do not claim to catch all vulnerabilities. Though we are always trying to update our vulnerability database and generate alerts with our most up-to-date information, we will not be able to catch everything or tell you about 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 Dependabot de GitHub alerts

You can see all of the alerts that affect a particular project in the repository's dependency graph. For more information, see "Viewing and updating vulnerable dependencies in your repository."

By default, we notify people with admin permissions in the affected repositories about new Alertas del Dependabot de GitHub.

You can choose the delivery method for notifications, as well as the frequency at which the notifications are sent to you. For more information, see "Configuring notifications for vulnerable dependencies."

You can also see all the Alertas del Dependabot de GitHub that correspond to a particular vulnerability in the GitHub Advisory Database. For more information about advisory data, see "Browsing security vulnerabilities in the GitHub Advisory Database."

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

O, learn how to contribute.