codeql
Audited by Runlayer on Feb 27, 2026
Malicious tool definition detected
Installed model packs:** ```bash codeql resolve qlpacks 2>/dev/null | grep -iE 'model|extension' ``` **If any found:** Report to user what was found and finish. These will be picked up by the run-analysis workflow's model pack detection (Step 2b).
Malicious tool definition detected
| head -20 # Estimate file counts echo "Total source files:" fd -t f -e py -e js -e ts -e go -e rb | wc -l echo "In node_modules:" fd -t f -e js -e ts node_modules 2>/dev/null | wc -l ``` **Create exclusion config:** ```yaml # codeql-config.yml paths-ignore: # Package managers - node_modules - vendor - venv - .venv # Third-party code - third_party - external - deps # Generated/minified - "**/*.min.js" - "**/*.bundle.js" - "**/generated/**" - "**/dist/**" # Tests (optional) # - "**/test/**" # - "
"Abort" ``` --- ## Final Report **Finalize the log file:** ```bash echo "=== Build Complete ===" >> "$LOG_FILE" echo "Finished: $(date -Iseconds)" >> "$LOG_FILE" echo "Final database: $DB_NAME" >> "$LOG_FILE" echo "Successful method: <METHOD>" >> "$LOG_FILE" echo "Final command: <EXACT_COMMAND>" >> "$LOG_FILE" codeql resolve database -- "$DB_NAME" >> "$LOG_FILE" 2>&1 ``` **Report to user:** ``` ## Database Build Complete **Database:** $DB_NAME **Language:** <LANG> **Build method:** autobuild | c
Malicious tool definition detected
Tool passed security scan
Malicious tool definition detected
Malicious tool definition detected
Verify CodeQL is installed command -v codeql >/dev/null 2>&1 && codeql --version || echo "NOT INSTALLED" # 2. Check for existing database ls -dt codeql_*.db 2>/dev/null | head -1 ``` Then execute the full pipeline: **build database → create data extensions → run analysis** using the workflows below.
Tool passed security scan
Tool passed security scan
Passed Files (2)Click to expand
Tool passed security scan
Tool passed security scan