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. Depending on the severity level and the way your project uses the dependency, vulnerabilities can cause a range of problems for your project or the people who use it. You can track and resolve vulnerabilities for certain types of dependencies in your GitHub repository.
If GitHub detects a vulnerability from the GitHub Advisory Database or WhiteSource in one of the dependencies in your repository's dependency graph, we'll send you an alert. For more information about the GitHub Advisory Database, see "Browsing security vulnerabilities in the GitHub Advisory Database."
When a new vulnerability is added to the GitHub Advisory Database, we identify public repositories (and private repositories that have opted in to vulnerability detection) that use the affected version of the dependency, send a Dependabot de GitHub alert to repository maintainers, and generate a Dependabot de GitHub security update.
Each Dependabot alert includes a severity level, a link to the affected file in your project, and a link to a pull request containing a security update that resolves the vulnerability. When available, the alert will include further details about the vulnerability.
You can see all of the alerts affecting a particular project on the repository's Security tab or in the repository's dependency graph. For more information, see "Viewing and updating vulnerable dependencies in your repository."
We send Dependabot alerts to people with admin permissions in the affected repositories by default. GitHub never publicly discloses identified vulnerabilities for any repository. You can also enable Dependabot alerts for additional people or teams working in organization-owned repositories. For more information, see "Managing alerts for vulnerable dependencies in your organization's repositories."
Actualizaciones de seguridad del Dependabot de GitHub update vulnerable dependencies to the minimum version that resolves the vulnerability. Security updates are automatically enabled in repositories that use the dependency graph and Alertas del Dependabot de GitHub, but you can choose to disable automatic pull requests and generate security updates manually instead. For more information, see "Configuring Actualizaciones de seguridad del Dependabot de GitHub."
GitHub detects and alerts on vulnerable dependencies in public repositories by default. To receive Alertas del Dependabot de GitHub for vulnerable dependencies in a private repository, an owner of or person with admin access to the repository must enable the dependency graph and Alertas del Dependabot de GitHub in the repository. For more information, see "Managing data use settings for your private repository."
For a list of the supported languages that GitHub can detect vulnerabilities and dependencies for, see "Listing the packages that a repository depends on."
Note: GitHub'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.
By default, you will receive Alertas del Dependabot de GitHub by email, grouped by the specific vulnerability. 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 user interface. For more information, see Configuring notifications ."
Las notificaciones de correo electrónico para las alertas de seguridad que afectan a uno o más de tus repositorios incluyen aquellas del campo de encabezado de
X-GitHub-Severity. Puedes utilizar el valor de el campo de encabezado de
X-GitHub-Severity para filtrar las notificaciones de correo electrónico para las alertas de seguridad. For more information, see "Configuring notifications."