Viewing code scanning logs

About your code scanning configuration

You can use a variety of tools to configure code scanning in your repository. For more information, see Establecimiento de la configuración predeterminada para el examen del código and Establecimiento de la configuración avanzada para el examen del código.

The log and diagnostic information available to you depends on the method you use for code scanning in your repository. You can check the type of code scanning you're using in the Security tab of your repository, by using the Tool drop-down menu in the alert list. For more information, see Evaluación de alertas de análisis de código para el repositorio.

About analysis and diagnostic information

You can see analysis and diagnostic information for code scanning run using CodeQL analysis on GitHub.

Analysis information is shown for the most recent analysis in a header at the top of the list of alerts. For more information, see Evaluación de alertas de análisis de código para el repositorio.

Diagnostic information is displayed in the Action workflow logs and consists of summary metrics and extractor diagnostics. For information about accessing code scanning logs on GitHub, see Viewing the logging output from code scanning below.

If you're using the CodeQL CLI outside GitHub, you'll see diagnostic information in the output generated during database analysis. This information is also included in the SARIF results file you upload to GitHub with the code scanning results.

For information about the CodeQL CLI, see Análisis del código con consultas de CodeQL.

About summary metrics

Las métricas de resumen incluyen:

• Las líneas de código en la base de código (que se utilizan como línea base), antes de la creación y extracción de la base de datos de CodeQL
• Las líneas de código en la base de datos de CodeQL que se extrajeron del código, incluyendo las bibliotecas externas y los archivos autogenerados
• Las líneas de código en la base de datos de CodeQL, excluyendo los archivos autogenerados y las bibliotecas externas

About CodeQL source code extraction diagnostics

El diagnóstico de extractor solo cubre los archivos que se vieron durante el análisis, las métricas incluyen:

• Cantidad de archivos que se analizaron con éxito
• Cantidad de archivos que generaron errores de extractor durante la creación de la base de datos
• Cantidad de archivos que generaron alertas del extractor durante la creación de la base de datos

You can see more detailed information about CodeQL extractor errors and warnings that occurred during database creation by enabling debug logging. For more information, see Los registros no son lo suficientemente detallados.

Viewing the logging output from code scanning

This section applies to code scanning run using GitHub Actions (CodeQL or third-party).

After configuring code scanning for your repository, you can watch the output of the actions as they run.

1. En el nombre del repositorio, haz clic en Actions.

   

   You'll see a list that includes an entry for running the code scanning workflow. The text of the entry is the title you gave your commit message.

   

2. Click the entry for the code scanning workflow.

   Nota:

   If you are looking for the CodeQL workflow run triggered by enabling default setup, the text of the entry is "CodeQL."

3. Click the job name on the left. For example, Analyze (LANGUAGE).

   

4. Review the logging output from the actions in this workflow as they run.

5. Optionally, to see more detail about the commit that triggered the workflow run, click the short commit hash. The short commit hash is 7 lowercase characters immediately following the commit author's username.

6. Once all jobs are complete, you can view the details of any code scanning alerts that were identified. For more information, see Evaluación de alertas de análisis de código para el repositorio.

Determining whether code scanning default setup used any private registries

Code scanning default setup includes a Setup proxy or registries step. When you are looking at a log file for default setup, you can expand this step. If the step includes:

• Using registries_credentials input. At least one private registry is configured for the organization.

• Credentials loaded for the following registries:

  • No further output in the step. Access was unsuccessful.
  • Type: nuget_feed; Default set up accessed a private Nuget feed.
  • Type: maven_repository; Default set up accessed a private Maven repository.

For more information, see Concesión de acceso a las características de seguridad a registros privados.