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 performs a scan to detect vulnerable dependencies and sends Las alertas del dependabot when:
-
New advisory data is synchronized to tu instancia de GitHub Enterprise Server each hour from GitHub.com. Para obtener más información sobre los datos de las asesorías, consulta la sección "Buscar vulnerabilidades de seguridad en la GitHub Advisory Database" dentro de la documentación de GitHub.com.
Note: Only advisories that have been reviewed by GitHub will trigger Las alertas del dependabot.
-
The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on. For more information, see "About the dependency graph."
For a list of the ecosystems that GitHub Enterprise Server 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.
Las alertas del dependabot for vulnerable dependencies
Los propietarios de empresas deben habilitar las Las alertas del dependabot para las dependencias vulnerables de tu instancia de GitHub Enterprise Server antes de que puedas utilizar esta característica. Para obtener más información, consulta la sección "Habilitar la Dependabot en tu empresa".
When GitHub Enterprise Server identifies a vulnerable dependency, we generate a Dependabot alert and display it in the repository's dependency graph. The alert includes information about a fixed version. GitHub Enterprise Server may also notify 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 Server'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 Las alertas del dependabot
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 Las alertas del dependabot.
Puedes elegir el método de entrega de las notificaciones, así como la frecuencia en las que se te envían. For more information, see "Configuring notifications for vulnerable dependencies."
You can also see all the Las alertas del dependabot that correspond to a particular vulnerability in the GitHub Advisory Database. Para obtener más información sobre los datos de las asesorías, consulta la sección "Buscar vulnerabilidades de seguridad en la GitHub Advisory Database" dentro de la documentación de GitHub.com.