codeql

Name: codeql
Availability: InStock
Author: Superlend

Detect security vulnerabilities in code using CodeQL queries.

Updated Jul 10, 2025

Search Tags:#security #CI/CD #queries #static-analysis #codeql #data-flow #taint-tracking

Ready to run

npx skills add https://github.com/Superlend/superloop-core-contracts --skill codeql-superlend

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: codeql
Source: https://github.com/Superlend/superloop-core-contracts/tree/main/.cursor/skills/static-analysis/skills/codeql
Command: npx skills add https://github.com/Superlend/superloop-core-contracts --skill codeql-superlend

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

CodeQL static analysis enables security vulnerability detection, taint tracking, and data-flow analysis by querying codebases with CodeQL queries. The skill guides you through building CodeQL databases, writing custom QL queries, and integrating CodeQL into CI/CD pipelines.

Core Features & Use Cases

CodeQL Database Management: Build and manage databases for multiple languages to enable precise security analysis.
Custom Queries: Create and run QL queries to detect specific vulnerabilities and data-flow issues.
CI/CD Integration: Embed CodeQL analyses into automated pipelines for ongoing security checks.
Security Audits: Conduct comprehensive audits across repositories to identify taint paths and interprocedural flows.

Quick Start

Install CodeQL CLI, create a database for your project, and run a sample query to verify setup.

Frequently Asked Questions about codeql

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I detect security vulnerabilities using static analysis on my codebase?▼

Static analysis detects security vulnerabilities by querying your codebase with CodeQL. You build a language-specific CodeQL database, run custom QL queries against it, and analyze the resulting data-flow and taint-tracking paths to identify interprocedural security issues.

How do I integrate CodeQL analysis into my CI/CD pipeline for ongoing security checks?▼

Integrating CodeQL into CI/CD pipelines automates continuous security vulnerability detection. You add steps to create CodeQL databases during the build process, execute custom queries, and package the analysis results to fail workflows when security vulnerabilities or taint paths are found.

Do I need the CodeQL CLI installed to run custom queries for taint tracking?▼

Yes, you need the CodeQL CLI installed to run custom queries for taint tracking. The CLI is required to create CodeQL databases for your project's source code, execute the QL queries, and package the data-flow analysis results.

How do I build a CodeQL database for multiple programming languages?▼

Building a CodeQL database for multiple languages requires language-specific build steps. You use the CodeQL CLI to capture compilation details during the build process, creating separate databases that enable precise security analysis and interprocedural data-flow tracking across your project.

What is the best way to write custom QL queries to find specific data-flow issues?▼

Writing custom QL queries to find data-flow issues involves using CodeQL's taint-tracking libraries. You define source and sink points in your code, and the query analyzes the generated database to detect interprocedural paths where untrusted data flows to vulnerable operations.

Can I conduct a comprehensive security audit across my repositories using CodeQL?▼

Yes, you can conduct comprehensive security audits across repositories using CodeQL. By generating databases for each repository and running targeted queries, you can identify taint paths, data-flow vulnerabilities, and security issues across multiple projects.