Skip to main content

This version of GitHub Enterprise was discontinued on 2023-07-06. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise. For help with the upgrade, contact GitHub Enterprise support.

bqrs interpret

[Plumbing] Interpret data in a single BQRS.

GitHub CodeQL is licensed on a per-user basis upon installation. You can use CodeQL only for certain tasks under the license restrictions. For more information, see "About the CodeQL CLI."

If you have a GitHub Advanced Security license, you can use CodeQL for automated analysis, continuous integration, and continuous delivery. For more information, see "About GitHub Advanced Security."

This content describes the most recent release of the CodeQL CLI. For more information about this release, see

To see details of the options available for this command in an earlier release, run the command with the --help option in your terminal.


codeql bqrs interpret --format=<format> --output=<output> -t=<String=String> [--threads=<num>] [--source-archive=<sourceArchive>] [--source-location-prefix=<sourceLocationPrefix>] <options>... -- <bqrs-file>


[Plumbing] Interpret data in a single BQRS.

A command that interprets a single BQRS file according to the provided metadata and generates output in the specified format.

Primary options


[Mandatory] The BQRS file to interpret.


[Mandatory] The format in which to write the results. One of:

csv: Formatted comma-separated values, including columns with both rule and alert metadata.

sarif-latest: Static Analysis Results Interchange Format (SARIF), a JSON-based format for describing static analysis results. This format option uses the most recent supported version (v2.1.0). This option is not suitable for use in automation as it will produce different versions of SARIF between different CodeQL versions.

sarifv2.1.0: SARIF v2.1.0.

graphtext: A textual format representing a graph. Only compatible with queries with @kind graph.

dgml: Directed Graph Markup Language, an XML-based format for describing graphs. Only compatible with queries with @kind graph.

dot: Graphviz DOT language, a text-based format for describing graphs. Only compatible with queries with @kind graph.

-o, --output=<output>

[Mandatory] The output path to write results to. For graph formats this should be a directory, and the result (or results if this command supports interpreting more than one query) will be written within that directory.


[Mandatory] A query metadata key value pair. Repeat for each piece of metadata. At least the keys 'kind' and 'id' must be specified. Keys do not need to be prefixed with @.


The maximum number of paths to produce for each alert with paths. (Default: 4)


[SARIF formats only] Include the full file contents for all files referenced in at least one result.


[SARIF formats only] Include code snippets for each location mentioned in the results, with two lines of context before and after the reported location.


[SARIF formats only] Include Markdown query help in the results. It loads query help for /path/to/query.ql from the /path/to/ file. This option has no effect when passed to codeql bqrs interpret.


[SARIF formats only] Place the rule object for each query under its corresponding QL pack in the <run>.tool.extensions property. This option has no effect when passed to codeql bqrs interpret.


[SARIF formats only] For alerts that have multiple causes, include them as a Markdown-formatted itemized list in the output in addition to as a plain string.


[SARIF formats only] Produce one result per message, rather than one result per unique location.


The format in which to produce locations in CSV output. One of: uri, line-column, offset-length. (Default: line-column)


A format string defining the format in which to produce file location URLs in DOT output. The following place holders can be used {path} {start:line} {start:column} {end:line} {end:column}, {offset}, {length}


[SARIF formats only] Specify a category for this analysis to include in the SARIF output. A category can be used to distinguish multiple analyses performed on the same commit and repository, but on different languages or different parts of the code.

If you analyze the same version of a code base in several different ways (e.g., for different languages) and upload the results to GitHub for presentation in Code Scanning, this value should differ between each of the analyses, which tells Code Scanning that the analyses supplement rather than supersede each other. (The values should be consistent between runs of the same analysis for different versions of the code base.)

This value will appear (with a trailing slash appended if not already present) as the <run>.automationId property in SARIF v1, the <run>.automationLogicalId property in SARIF v2, and the <run> property in SARIF v2.1.0.

-j, --threads=<num>

The number of threads used for computing paths.

Defaults to 1. You can pass 0 to use one thread per core on the machine, or -N to leave N cores unused (except still use at least one thread).


[SARIF only] A key value pair to add to the generated SARIF 'run' property bag. Can be repeated.


[SARIF only] The column kind used to interpret location columns. One of: utf8, utf16, utf32, bytes.


[SARIF only] Whether the unicode newline characters LS (Line Separator, U+2028) and PS (Paragraph Separator, U+2029) are considered as new lines when interpreting location line numbers.

Source archive options - must be given together or not at all

-s, --source-archive=<sourceArchive>

The directory or zip file containing the source archive.

-p, --source-location-prefix=<sourceLocationPrefix>

The file path on the original file system where the source code was stored.

Common options

-h, --help

Show this help text.


[Advanced] Give option to the JVM running the command.

(Beware that options containing spaces will not be handled correctly.)

-v, --verbose

Incrementally increase the number of progress messages printed.

-q, --quiet

Incrementally decrease the number of progress messages printed.


[Advanced] Explicitly set the verbosity level to one of errors, warnings, progress, progress+, progress++, progress+++. Overrides -v and -q.


[Advanced] Write detailed logs to one or more files in the given directory, with generated names that include timestamps and the name of the running subcommand.

(To write a log file with a name you have full control over, instead give --log-to-stderr and redirect stderr as desired.)