fewer-lines-scanned-than-expected.md

title	shortTitle	intro	allowTitleToDifferFromFilename	versions	redirect_from
CodeQL scanned fewer lines than expected	Fewer lines scanned than expected	If {% data variables.product.prodname_codeql %} analyzed less code than you expected, you may need to use a custom build command.	true	fpt ghes ghec * * *	/code-security/code-scanning/troubleshooting-code-scanning/codeql-scanned-fewer-lines-than-expected

About analysis of compiled languages

{% ifversion codeql-no-build %}When compiled languages are analyzed using the autobuild or manual build mode,{% elsif ghes %}For compiled languages like {% data variables.code-scanning.compiled_languages %},{% endif %} {% data variables.product.prodname_codeql %} only scans files that are built during the analysis. Therefore the number of lines of code scanned will be lower than expected if some of the source code isn't compiled correctly. This can happen for several reasons:

1. The {% data variables.product.prodname_codeql %} autobuild feature uses heuristics to build the code in a repository. However, sometimes this approach results in an incomplete analysis of a repository. For example, when multiple build.sh commands exist in a single repository, the analysis may not be complete since the autobuild step will only execute one of the commands, and therefore some source files may not be compiled.

2. Some compilers do not work with {% data variables.product.prodname_codeql %} and can cause issues while analyzing the code. For example, most vendor-specific C compilers will not be recognized by {% data variables.product.prodname_codeql %}. C code will need to be compiled with a recognized compiler (for example GCC, Clang or MSVC) in order to be analyzed.

If your {% data variables.product.prodname_codeql %} analysis scans fewer lines of code than expected, you can try {% ifversion codeql-no-build %}changing the build mode to manual and specifying build commands if your workflow specifies a build mode, {% endif %} replacing the autobuild step with build commands if your workflow contains an autobuild step, or inspecting the copy of the source files in the {% data variables.product.prodname_codeql %} database.

{% ifversion codeql-no-build %}Change to a manual build process{% elsif ghes %}Replace the autobuild step{% endif %}

Replace the autobuild process with the same build commands you would use in production. This makes sure that {% data variables.product.prodname_codeql %} knows exactly how to compile all of the source files you want to scan. For more information about defining build steps, see {% ifversion codeql-no-build %}AUTOTITLE{% elsif ghes %}AUTOTITLE{% endif %}.

Inspect the copy of the source files in the {% data variables.product.prodname_codeql %} database

You may be able to understand why some source files haven't been analyzed by inspecting the copy of the source code included with the {% data variables.product.prodname_codeql %} database. To obtain the database from your Actions workflow, modify the init step of your {% data variables.product.prodname_codeql %} workflow file and set debug: true.

- name: Initialize CodeQL
  uses: {% data reusables.actions.action-codeql-action-init %}
  with:
    debug: true

This uploads the database as an actions artifact that you can download to your local machine. For more information, see AUTOTITLE.

The artifact will contain an archived copy of the source files scanned by {% data variables.product.prodname_codeql %} called src.zip. If you compare the source code files in the repository and the files in src.zip, you can see which types of file are missing. Once you know what types of file are not being analyzed, it is easier to understand how you may need to change the workflow for {% data variables.product.prodname_codeql %} analysis.