What do Extractors provide in the CodeQL workflow?

What do Extractors provide in the CodeQL workflow?

• A. Relational data and source references for each input file to build a CodeQL database
• B. A collection of compiled binaries for analysis
• C. A way to export issue trackers
• D. A log of secret scanning alerts

Answer: (A)

Extractors supply the structured facts that CodeQL uses to build its database. They read each input source file and emit relational data—such as AST structures, symbol definitions and references, and other code relationships—together with source references (file paths and positions) so every fact can be traced back to its origin. This collection of facts forms the CodeQL database, enabling queries to analyze how different parts of the code relate and to detect patterns or vulnerabilities. The other options don’t fit because extractors don’t deal with compiled binaries, exporting issue trackers, or logging secret scanning alerts.

Extractors supply the structured facts that CodeQL uses to build its database. They read each input source file and emit relational data—such as AST structures, symbol definitions and references, and other code relationships—together with source references (file paths and positions) so every fact can be traced back to its origin. This collection of facts forms the CodeQL database, enabling queries to analyze how different parts of the code relate and to detect patterns or vulnerabilities. The other options don’t fit because extractors don’t deal with compiled binaries, exporting issue trackers, or logging secret scanning alerts.