CodeQL documentation

Getting started with the CodeQL CLI

To run CodeQL commands, you need to set up the CLI so that it can access the tools, queries, and libraries required to create and analyze databases.

License notice

If you don’t have an Enterprise license then, by installing this product, you are agreeing to the GitHub CodeQL Terms and Conditions.

GitHub CodeQL is licensed on a per-user basis. Under the license restrictions, you can CodeQL to perform the following tasks:

  • To perform academic research.
  • To demonstrate the software.
  • To test CodeQL queries that are released under an OSI-approved License to confirm that new versions of those queries continue to find the right vulnerabilities.

where “OSI-approved License” means an Open Source Initiative (OSI)-approved open source software license.

If you are working with an Open Source Codebase (that is, a codebase that is released under an OSI-approved License) you can also use CodeQL for the following tasks:

  • To perform analysis of the Open Source Codebase.
  • If the Open Source Codebase is hosted and maintained on, to generate CodeQL databases for or during automated analysis, continuous integration, or continuous delivery.

CodeQL can’t be used for automated analysis, continuous integration or continuous delivery, whether as part of normal software engineering processes or otherwise, except in the express cases set forth herein. For these uses, contact the sales team.

Setting up the CodeQL CLI

The CodeQL CLI can be set up to support many different use cases and directory structures. To get started quickly, we recommend adopting a relatively simple setup, as outlined in the steps below.

If you use Linux, Windows, or macOS version 10.14 (“Mojave”) or earlier, simply follow the steps below. For macOS version 10.15 (“Catalina”) or newer, steps 1 and 4 are slightly different—for further details, see the sections labeled Information for macOS “Catalina” (or newer) users.

For information about installing the CodeQL CLI in a CI system to create results to display in GitHub as code scanning alerts, see Installing CodeQL CLI in your CI system in the GitHub documentation.

1. Download the CodeQL CLI zip package

The CodeQL CLI download package is a zip archive containing tools, scripts, and various CodeQL-specific files. If you don’t have an Enterprise license then, by downloading this archive, you are agreeing to the GitHub CodeQL Terms and Conditions.


There are several different versions of the CLI available to download, depending on your use case:

  • If you want to use the most up to date CodeQL tools and features, download the version tagged latest.
  • If you want to create CodeQL databases to upload to LGTM Enterprise, download the version that is compatible with the relevant LGTM Enterprise version number. Compatibility information is included in the description for each release on the CodeQL CLI releases page on GitHub. Using the correct version of the CLI ensures that your CodeQL databases are compatible with your version of LGTM Enterprise. For more information, see Preparing CodeQL databases to upload to LGTM in the LGTM admin help.

If you use Linux, Windows, or macOS version 10.14 (“Mojave”) or earlier, simply download the zip archive for the version you require.

If you want the CLI for a specific platform, download the appropriate file. Alternatively, you can download, which contains the CLI for all supported platforms.

Information for macOS “Catalina” (or newer) users

macOS “Catalina” (or newer)

If you use macOS version 10.15 (“Catalina”), version 11 (“Big Sur”), or the upcoming version 12 (“Monterey”), you need to ensure that your web browser does not automatically extract zip files. If you use Safari, complete the following steps before downloading the CodeQL CLI zip archive:

  1. Open Safari.
  2. From the Safari menu, select Preferences….
  3. Click the General Tab.
  4. Ensure the check-box labeled Open “safe” files after downloading. is unchecked.

2. Create a new CodeQL directory

Create a new directory where you can place the CLI and any queries and libraries you want to use. For example, $HOME/codeql-home.

The CLI’s built-in search operations automatically look in all of its sibling directories for the files used in database creation and analysis. Keeping these components in their own directory prevents the CLI searching unrelated sibling directories while ensuring all files are available without specifying any further options on the command line.

3. Obtain a local copy of the CodeQL queries

The CodeQL repository contains the queries and libraries required for CodeQL analysis of C/C++, C#, Java, JavaScript/TypeScript, Python, and Ruby. Clone a copy of this repository into codeql-home.

By default, the root of the cloned repository will be called codeql. Rename this folder codeql-repo to avoid conflicting with the CodeQL CLI that you will extract in step 4. If you use git on the command line, you can clone and rename the repository in a single step by running git clone codeql-repo in the codeql-home folder.

The CodeQL libraries and queries for Go analysis live in the CodeQL for Go repository. Clone a copy of this repository into codeql-home.

The cloned repositories should have a sibling relationship. For example, if the root of the cloned CodeQL repository is $HOME/codeql-home/codeql-repo, then the root of the cloned CodeQL for Go repository should be $HOME/codeql-home/codeql-go.

Within these repositories, the queries and libraries are organized into QL packs. Along with the queries themselves, QL packs contain important metadata that tells the CodeQL CLI how to process the query files. For more information, see “About QL packs.”


There are different versions of the CodeQL queries available for different users. Check out the correct version for your use case:

  • For the queries used on, check out the branch. You should use this branch for databases you’ve built using the CodeQL CLI, fetched from code scanning on GitHub, or recently downloaded from The queries on the branch are more likely to be compatible with the latest CLI, so you’ll be less likely to have to upgrade newly-created databases than if you use the main branch. Older databases may need to be upgraded before you can analyze them.
  • For the most up to date CodeQL queries, check out the main branch. This branch represents the very latest version of CodeQL’s analysis. Even databases created using the most recent version of the CLI may have to be upgraded before you can analyze them. For more information, see “Upgrading CodeQL databases.”
  • For the queries used in a particular LGTM Enterprise release, check out the branch tagged with the relevant release number. For example, the branch tagged v1.27.0 corresponds to LGTM Enterprise 1.27. You must use this version if you want to upload data to LGTM Enterprise. For further information, see Preparing CodeQL databases to upload to LGTM in the LGTM admin help.

4. Extract the zip archive

For Linux, Windows, and macOS users (version 10.14 “Mojave”, and earlier) simply extract the zip archive into the directory you created in step 2.

For example, if the path to your copy of the CodeQL repository is $HOME/codeql-home/codeql-repo, then extract the CLI into $HOME/codeql-home/.

Information for macOS “Catalina” (or newer) users

macOS “Catalina”

macOS “Catalina”, “Big Sur”, or “Monterey” users should run the following commands in the Terminal, where ${install_loc} is the path to the directory you created in step 2:

  1. mv ~/Downloads/codeql*.zip ${install_loc}
  2. cd ${install_loc}
  3. /usr/bin/xattr -c codeql*.zip
  4. unzip codeql*.zip

5. Launch codeql

Once extracted, you can run CodeQL processes by running the codeql executable in a couple of ways:

  • By executing <extraction-root>/codeql/codeql, where <extraction-root> is the folder where you extracted the CodeQL CLI package.
  • By adding <extraction-root>/codeql to your PATH, so that you can run the executable as just codeql.

At this point, you can execute CodeQL commands. For a full list of the CodeQL CLI commands, see the “CodeQL CLI manual.”


If you add codeql to your PATH, it can be accessed by CodeQL for Visual Studio Code to compile and run queries. For more information about configuring VS Code to access the CodeQL CLI, see “Setting up CodeQL in Visual Studio Code.”

6. Verify your CodeQL CLI setup

CodeQL CLI has subcommands you can execute to verify that you are correctly set up to create and analyze databases:

  • Run codeql resolve languages to show which languages are available for database creation. This will list the languages supported by default in your CodeQL CLI package.
  • Run codeql resolve qlpacks to show which QL packs the CLI can find. This will display the names of the QL packs included in the CodeQL repositories: codeql-cpp, codeql-csharp, codeql-go, codeql-java, codeql-javascript, and codeql-python. The CodeQL repositories also contain ‘upgrade’ packs and ‘legacy’ packs. Upgrade packs are used by the CLI when you want to upgrade a database so that it can be analyzed with a newer version of the CodeQL toolchain than was used to create it. Legacy packs ensure that custom queries and libraries created using older products are compatible with your version of CodeQL.

Using two versions of the CodeQL CLI

If you want to use the latest CodeQL features to execute queries or CodeQL tests, but also want to prepare databases that are compatible with a specific version of LGTM Enterprise, you may need to install two versions of the CLI. The recommended directory setup depends on which versions you want to install:

  • If both versions are 2.0.2 (or newer), you can unpack both CLI archives in the same parent directory.
  • If at least one of the versions is 2.0.1 (or older), the unpacked CLI archives cannot be in the same parent directory, but they can share the same grandparent directory. For example, if you unpack version 2.0.2 into $HOME/codeql-home/codeql-cli, the older version should be unpacked into $HOME/codeql-older-version/old-codeql-cli. Here, the common grandparent is the $HOME directory.
  • © GitHub, Inc.
  • Terms
  • Privacy