Skip to main content
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.

Viewing and updating Dependabot alerts

If GitHub Enterprise Cloud discovers insecure dependencies in your project, you can view details on the Dependabot alerts tab of your repository. Then, you can update your project to resolve or dismiss the alert.

Repository administrators and organization owners can view and update dependencies, as well as users and teams with explicit access.

La pestaña de Las alertas del dependabot de tu repositorio lista todas lasLas alertas del dependabot abiertas y cerradas, así como las Actualizaciones de seguridad del dependabot correspondientes. Puedes filtrar las alertas por paquete, ecosistema o manifiesto. You can sort the list of alerts, and you can click into specific alerts for more details. You can also dismiss or reopen alerts, either one by one or by selecting multiple alerts at once. For more information, see "About Las alertas del dependabot."

Puedes habilitar las alertas de seguridad automáticas para cualquier repositorio que utilice Las alertas del dependabot y la gráfica de dependencias. Para obtener más información, consulta la sección "Acerca de las Actualizaciones de seguridad del dependabot".

Acerca de las actualizaciones para las dependencias vulnerables en tu repositorio

GitHub Enterprise Cloud generates Las alertas del dependabot when we detect that your codebase is using dependencies with known security risks. Para los repositorios en donde se habilitan las Actualizaciones de seguridad del dependabot cuando GitHub Enterprise Cloud detecta una dependencia vulnerable en la rama predeterminada, Dependabot crea una solicitud de cambios para arreglarla. La solicitud de extracción mejorará la dependencia a la versión segura mínima que sea posible y necesaria para evitar la vulnerabilidad.

Puedes clasificar y filtrar las Las alertas del dependabot con los menús desplegables en la pestaña de Las alertas del dependabot o tecleando filtros tales como pares de key:value en la barra de búsqueda. The available filters are repository (for example, repo:my-repository), package (for example, package:django), ecosystem (for example, ecosystem:npm), manifest (for example, manifest:webwolf/pom.xml), state (for example, is:open), and whether an advisory has a patch (for example, has: patch). You can also filter alerts with dependency scope data using scope, for example: scope:development or scope:runtime. With scope:development, the list of alerts will only show dependencies used during development, not production.

Cada alerta del Dependabot tiene un identificador numérico único y la pestaña de Las alertas del dependabot lista una alerta por cada vulnerabilidad detectada. Las Las alertas del dependabot tradicionales agrupan vulnerabilidades por dependencia y generan una sola alerta por dependencia. Si navegas a una alerta tradicional del Dependabot, se te redirigirá a una pestaña de Las alertas del dependabot filtradas para este paquete.

Supported ecosystems and manifests for dependency scope

The table below summarizes whether dependency scope is supported for various ecosystems and manifests, that is, whether Dependabot can identify if a dependency is used for development or production.

LenguajeEcosystemManifest fileDependency scope supported
GoMódulos de Gogo.modNo, defaults to runtime
GoMódulos de Gogo.sumNo, defaults to runtime
JavaMavenpom.xmltest maps to development, else scope defaults to runtime
JavaScriptnpmpackage.json
JavaScriptnpmpackage-lock.json
JavaScriptyarn v1yarn.lockNo, defaults to runtime
PHPComposercomposer.json
PHPComposercomposer.lock
PythonPoetrypoetry.lock
PythonPoetrypyproject.toml
Pythonpiprequirements.txt✔ Scope is development if the filename contains test or dev, else it is runtime
Pythonpippipfile.lock
Pythonpippipfile
RubyRubyGemsGemfile
RubyRubyGemsGemfile.lockNo, defaults to runtime
RustCargoCargo.toml
RustCargoCargo.lockNo, defaults to runtime
YAMLGitHub Actions-No, defaults to runtime
.NET (C#, F#, VB, etc.)NuGet.csproj / .vbproj .vcxproj / .fsprojNo, defaults to runtime
.NETNuGetpackages.configNo, defaults to runtime
.NETNuGet.nuspec✔ When the tag != runtime

Alerts for packages listed as development dependencies are marked with the Development label on the Las alertas del dependabot page and are also available for filtering via the scope filter. Screenshot showing the "Development" label in the list of alerts

The alert details page of alerts on development-scoped packages shows a "Tags" section containing a Development label. Screenshot showing the "Tags" section in the alert details page

About the detection of calls to vulnerable functions

Notas:

  • The detection of calls to vulnerable functions by Dependabot is in beta and subject to change.

  • Detection of vulnerable calls is included in GitHub Enterprise Cloud for public repositories. To detect vulnerable calls in private repositories owned by organizations, your organization must have a license for GitHub Advanced Security. Para obtener más información, consulta la sección "Acerca de GitHub Advanced Security".

When Dependabot tells you that your repository uses a vulnerable dependency, you need to determine what the vulnerable functions are and check whether you are using them. Once you have this information, then you can determine how urgently you need to upgrade to a secure version of the dependency.

For supported languages, Dependabot automatically detects whether you use a vulnerable function and adds the label "Vulnerable call" to affected alerts. You can use this information in the Las alertas del dependabot view to triage and prioritize remediation work more effectively.

Note: During the beta release, this feature is available only for new Python advisories created after April 14, 2022, and for a subset of historical Python advisories. GitHub is working to backfill data across additional historical Python advisories, which are added on a rolling basis. Vulnerable calls are highlighted only on the Las alertas del dependabot pages.

Screenshot showing an alert with the "Vulnerable call" label

You can filter the view to show only alerts where Dependabot detected at least one call to a vulnerable function using the has:vulnerable-calls filter in the search field.

For alerts where vulnerable calls are detected, the alert details page shows additional information:

  • One or more code blocks showing where the function is used.
  • An annotation listing the function itself, with a link to the line where the function is called.

Screenshot showing the alert details page for an alert with a "Vulnerable call" label

For more information, see "Reviewing and fixing alerts" below.

Viewing Las alertas del dependabot

  1. En GitHub.com, visita la página principal del repositorio.

  2. Debajo de tu nombre de repositorio, da clic en Seguridad. Pestaña de seguridad

  3. En la barra lateral de seguridad, da clic en Las alertas del dependabot. Si no encuentras esta opción, significa que no tienes acceso a las alertas de seguridad y necesitas que te lo otorguen. Para obtener más información, consulta la sección "Administrar los ajustes de seguridad y análisis de tu repositorio".Las alertas del dependabot tab

  4. Opcionalmente, para filtrar alertas, selecciona el menú desplegable de Repositorio, l Paquete, Ecosistema o Manifiesto y luego haz clic en el filtro que te gustaría aplicar. También puedes teclear filtros en la barra de búsqueda. For example, ecosystem:npm, has:patch or scope:development. Para ordenar las alertas, selecciona el menú desplegable Ordenar y luego haz clic en la opción por la cual te gustaría ordenarlas.

    You can also click a label on an alert to only show alerts of that type. For example, clicking the Development label in the list of alerts will only show alerts relating to dependencies used in development, not production. For information about the list of ecosystems supported, see "Supported ecosystems and manifests for dependency scope ."

    Captura de pantalla del filtro y menús de clasificación en la pestaña de las Las alertas del dependabot

  5. Click the alert that you would like to view. Alert selected in list of alerts

Reviewing and fixing alerts

It’s important to ensure that all of your dependencies are clean of any security weaknesses. When Dependabot discovers vulnerabilities or malware in your dependencies, you should assess your project’s level of exposure and determine what remediation steps to take to secure your application.

If a patched version of the dependency is available, you can generate a Dependabot pull request to update this dependency directly from a Dependabot alert. If you have Actualizaciones de seguridad del dependabot enabled, the pull request may be linked will in the Dependabot alert.

In cases where a patched version is not available, or you can’t update to the secure version, Dependabot shares additional information to help you determine next steps. When you click through to view a Dependabot alert, you can see the full details of the security advisory for the dependency including the affected functions. You can then check whether your code calls the impacted functions. This information can help you further assess your risk level, and determine workarounds or if you’re able to accept the risk represented by the security advisory.

For supported languages, Dependabot detects calls to vulnerable functions for you. When you view an alert labeled as "Vulnerable call", the details include the name of the function and a link to the code that calls it. Often you will be able to take decisions based on this information, without exploring further.

Fixing vulnerable dependencies

  1. Ver los detalles de una alerta. For more information, see "Viewing Las alertas del dependabot" (above).

  2. If you have Actualizaciones de seguridad del dependabot enabled, there may be a link to a pull request that will fix the dependency. Alternatively, you can click Create Dependabot security update at the top of the alert details page to create a pull request. Create Dependabot security update button

  3. Optionally, if you do not use Actualizaciones de seguridad del dependabot, you can use the information on the page to decide which version of the dependency to upgrade to and create a pull request to update the dependency to a secure version.

  4. Cuando estés listo para actualizar tu dependencia y resolver la vulnerabilidad, fusiona la solicitud de extracción.

    Each pull request raised by Dependabot includes information on commands you can use to control Dependabot. For more information, see "Managing pull requests for dependency updates."

Dismissing Las alertas del dependabot

Tip: You can only dismiss open alerts.

If you schedule extensive work to upgrade a dependency, or decide that an alert does not need to be fixed, you can dismiss the alert. Dismissing alerts that you have already assessed makes it easier to triage new alerts as they appear.

  1. Ver los detalles de una alerta. For more information, see "Viewing vulnerable dependencies" (above).
  2. Select the "Dismiss" dropdown, and click a reason for dismissing the alert. Unfixed dismissed alerts can be reopened later. Elegir una razón para descartar la alerta a través del menú desplegable de "Descartar"

Descartar varias alertas al mismo tiempo

  1. View the open Las alertas del dependabot. For more information, see "Viewing Las alertas del dependabot".
  2. Optionally, filter the list of alerts by selecting a dropdown menu, then clicking the filter that you would like to apply. También puedes teclear filtros en la barra de búsqueda.
  3. To the left of each alert title, select the alerts that you want to dismiss. Screenshot of open alerts with checkboxes emphasized
  4. Optionally, at the top of the list of alerts, select all alerts on the page. Screenshot of all open alerts selected
  5. Select the "Dismiss alerts" dropdown, and click a reason for dismissing the alerts. Screenshot of open alerts page with "Dismiss alerts" drop-down emphasized

Viewing and updating closed alerts

Tip: You can only reopen alerts that have been previously dismissed. Closed alerts that have already been fixed cannot be reopened.

  1. En GitHub.com, visita la página principal del repositorio.
  2. Debajo de tu nombre de repositorio, da clic en Seguridad. Pestaña de seguridad
  3. En la barra lateral de seguridad, da clic en Las alertas del dependabot. Si no encuentras esta opción, significa que no tienes acceso a las alertas de seguridad y necesitas que te lo otorguen. Para obtener más información, consulta la sección "Administrar los ajustes de seguridad y análisis de tu repositorio".Las alertas del dependabot tab
  4. Para solo ver las alertas cerradas, haz clic en Cerrada. Screenshot showing the "Closed" option
  5. Haz clic en la alerta que te gustaría ver o actualizar. Screenshot showing a highlighted dependabot alert
  6. Optionally, if the alert was dismissed and you wish to reopen it, click Reopen. Alerts that have already been fixed cannot be reopened. Screenshot showing the "Reopen" button

Reopening multiple alerts at once

  1. View the closed Las alertas del dependabot. For more information, see "Viewing and updating closed alerts" (above).
  2. To the left of each alert title, select the alerts that you want to reopen. Screenshot of closed alerts with checkboxes emphasized
  3. Optionally, at the top of the list of alerts, select all closed alerts on the page. Screenshot of closed alerts with all alerts selected
  4. Click Reopen to reopen the alerts. Alerts that have already been fixed cannot be reopened. Screenshot of closed alerts with "Reopen" button emphasized