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.

Managing code scanning alerts for your repository

From the security view, you can view, fix, or close alerts for potential vulnerabilities or errors in your project's code.

If you have write permission to a repository you can manage escaneo de código alerts for that repository.

Escaneo de código is available if you have an Advanced Security license.

En este artículo

Nota: Escaneo de código se encuentra acutalmente en beta y está sujeto a cambios. If your organization has an Advanced Security license, you can join the beta program.

About alerts from escaneo de código

You can set up escaneo de código to check the code in a repository using the default CodeQL analysis, a third-party analysis, or multiple types of analysis. When the analysis is complete, the resulting alerts are displayed alongside each other in the security view of the repository. Results from third-party tools or from custom queries may not include all of the properties that you see for alerts detected by GitHub's default CodeQL analysis. For more information, see "Enabling escaneo de código for a repository."

By default, escaneo de código analyzes your code periodically on the default branch and during pull requests. For information about managing alerts on a pull request, see "Triaging escaneo de código alerts in pull requests."

About alerts details

Each alert highlights a problem with the code and the name of the tool that identified it. You can see the line of code that triggered the alert, as well as properties of the alert, such as the severity and the nature of the problem. Alerts also tell you when the issue was first introduced. For alerts identified by CodeQL analysis, you will also see information on how to fix the problem.

Example alert from escaneo de código

If you enable escaneo de código using CodeQL, this can also detect data-flow problems in your code. Data-flow analysis finds potential security issues in code, such as: using data insecurely, passing dangerous arguments to functions, and leaking sensitive information.

When escaneo de código reports data-flow alerts, GitHub shows you how data moves through the code. Escaneo de código allows you to identify the areas of your code that leak sensitive information, and that could be the entry point for attacks by malicious users.

Viewing the alerts for a repository

Anyone with read permission for a repository can see escaneo de código annotations on pull requests. For more information, see "Triaging escaneo de código alerts in pull requests."

You need write permission to view a summary of all the alerts for a repository on the Security tab. By default, alerts are shown for the default branch.

  1. En GitHub Enterprise, 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 izquierda, da clic en alertas de escaneo de código. Opcionalmente, selecciona la herramienta de escaneo de código que utilizaste.
    pestaña de "Alertas de escaneo de código"
  4. Under "Escaneo de código," click the alert you'd like to explore.
    Summary of alerts
  5. Optionally, if the alert highlights a problem with data flow, click Show paths to display the path from the data source to the sink where it's used.
    The "Show paths" link on an alert
  6. Alerts from CodeQL analysis include a description of the problem. Click Show more for guidance on how to fix your code.
    Details for an alert

Fixing an alert

Anyone with write permission for a repository can fix an alert by committing a correction to the code. If the repository has escaneo de código scheduled to run on pull requests, it's best to raise a pull request with your correction. This will trigger escaneo de código analysis of the changes and test that your fix doesn't introduce any new problems. For more information, see "Configuring escaneo de código" and "Triaging escaneo de código alerts in pull requests."

If you have write permission for a repository, you can view fixed alerts by viewing the summary of alerts and clicking Closed. For more information, see "Viewing the alerts for a repository." The "Closed" list shows fixed alerts and alerts that users have closed.

Alerts may be fixed in one branch but not in another. You can use the "Branch" drop-down menu, on the summary of alerts, to check whether an alert is fixed in a particular branch.

Filtering alerts by branch

Closing an alert

Closing an alert is a way to resolve an alert that you don't think needs to be fixed. For example, an error in code that's used only for testing, or when the effort of fixing the error is greater than the potential benefit of improving the code.

  1. En GitHub Enterprise, 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 izquierda, da clic en alertas de escaneo de código. Opcionalmente, selecciona la herramienta de escaneo de código que utilizaste.

    pestaña de "Alertas de escaneo de código"

  4. Debajo de "Escaneo de Código", da clic en la alerta que quieras ver.

    Lista de alertas de escaneo de código

  5. Select the Close drop-down menu and click a reason for closing the alert.

    Choosing reason for closing the alert via the Close drop-down

If you close a CodeQL alert as a false positive result, for example because the code uses a sanitization library that isn't supported, consider contributing to the CodeQL repository and improving the analysis. For more information about CodeQL, see "Contributing to CodeQL."

Further reading

¿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.