Note: This article was migrated from the CodeQL documentation website in January 2023.
You can customize your CodeQL analyses by writing your own queries to highlight specific vulnerabilities or errors.
Note: Queries run with
database analyze have strict metadata requirements. You can also execute queries using the following plumbing-level subcommands:
- database run-queries, which outputs non-interpreted results in an intermediate binary format called BQRS.
- query run, which will output BQRS files, or print results tables directly to the command line. Viewing results directly in the command line may be useful for iterative query development using the CLI.
Queries run with these commands don’t have the same metadata requirements. However, to save human-readable data you have to process each BQRS results file using the bqrs decode plumbing subcommand. Therefore, for most use cases it’s easiest to use database analyze to directly generate interpreted results.
Before running a custom analysis you need to write a valid query, and save it in a file with a
.ql extension. There is extensive documentation available to help you write queries. For more information, see "CodeQL queries."
Query metadata is included at the top of each query file. It provides users with information about the query, and tells the CodeQL CLI how to process the query results.
When running queries with the
database analyze command, you must include the following two properties to ensure that the results are interpreted correctly:
Query identifier (
@id): a sequence of words composed of lowercase letters or digits, delimited by
-, identifying and classifying the query.
Query type (
@kind): identifies the query as a simple alert (
@kind problem), an alert documented by a sequence of code locations (
@kind path-problem), for extractor troubleshooting (
@kind diagnostic), or a summary metric (
Note: Metadata requirements may differ if you want to use your query with other applications. For more information, see "Metadata for CodeQL queries."