Nota: Escaneo de código se encuentra acutalmente en beta y está sujeto a cambios. To request access to the beta, join the waitlist.
About your escaneo de código setup
You can use a variety of tools to set up escaneo de código in your repository. For more information, see "Setting up escaneo de código for a repository."
The log and diagnostic information available to you depends on the method you use for escaneo de código in your repository. You can check the type of escaneo de código 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 "Managing escaneo de código alerts for your repository."
About analysis and diagnostic information
You can see analysis and diagnostic information for escaneo de código 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 "Managing code scanning alerts for your repository."
Diagnostic information is displayed in the Action workflow logs and consists of summary metrics and extractor diagnostics. For information about accessing escaneo de código logs on GitHub, see "Viewing the logging output from escaneo de código" 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 escaneo de código results.
For information about the CodeQL CLI, see "Running CodeQL CLI in your CI system."
About summary metrics
Summary metrics include:
- Lines of code in the codebase (used as a baseline), before creation and extraction of the CodeQL database
- Lines of code in the CodeQL database extracted from the code, including external libraries and auto-generated files
- Lines of code in the CodeQL database excluding auto-generated files and external libraries
About CodeQL source code extraction diagnostics
Extractor diagnostics only cover files that were seen during the analysis, metrics include:
- Number of files successfully analyzed
- Number of files that generated extractor errors during database creation
- Number of files that generated extractor warnings during database creation
Viewing the logging output from escaneo de código
This section applies to escaneo de código run using GitHub Actions (CodeQL or third-party).
After setting up escaneo de código for your repository, you can watch the output of the actions as they run.
-
Debajo del nombre de tu repositorio, da clic en Acciones.
You'll see a list that includes an entry for running the escaneo de código workflow. The text of the entry is the title you gave your commit message.
-
Click the entry for the escaneo de código workflow.
-
Click the job name on the left. For example, Analyze (LANGUAGE).
-
Review the logging output from the actions in this workflow as they run.
-
Once all jobs are complete, you can view the details of any escaneo de código alerts that were identified. For more information, see "Managing escaneo de código alerts for your repository."
Note: If you raised a pull request to add the escaneo de código workflow to the repository, alerts from that pull request aren't displayed directly on the Escaneo de código page until the pull request is merged. If any alerts were found you can view these, before the pull request is merged, by clicking the n alerts found link in the banner on the Escaneo de código page.
