Code quality and security

Composal vs GitHub CodeQL

CodeQL queries source models to identify code-level issues. Composal interacts with an application in a browser and records tested outcomes; neither form of evidence replaces the other.

See where each fits ↓

Two workflows, side by side

Composal

Composal sends AI browser agents to use your running web app and check the outcomes you care about. Define journeys as plain-English Scenarios, map existing flows with Discovery, or explore for bugs with Deep Scan. Runs keep recordings and reproduction steps so your team or coding agent can investigate a Finding.

Verify documentation →

GitHub CodeQL

Semantic code queries for security and correctness analysis

CodeQL builds a database of code and runs queries to find security vulnerabilities and correctness issues. Teams can use standard or custom queries.

What each tool does

“With setup” means you supply code or configuration. “Not confirmed” means support for this workflow needs checking with the vendor.

Composal and GitHub CodeQL workflow capabilities
Workflow	Composal	GitHub CodeQL
Run browser journeys	Yes Run saved browser Scenarios and return recordings and reproducible Findings.	No The documented product reviews or analyzes source changes; it does not execute browser journeys.
Map application workflows	Yes Discovery maps key application areas and user journeys.	Not confirmed Check whether this product includes this workflow in your intended plan and setup.
Explore for unexpected issues	Yes Deep Scan explores the running application and reports reproducible issues.	Not confirmed Check whether this product includes this workflow in your intended plan and setup.
Describe checks in plain English	Yes Author Scenarios around the intended user outcome, then review the steps and expected results.	Not confirmed Check whether this product includes this workflow in your intended plan and setup.
Run or inspect from a terminal	Yes Use the CLI to start and inspect verification runs and their Findings.	With setup Connect its specialist checks to your development workflow using supported integrations.
Source code review and analysis	No Use a dedicated tool for this specialist workflow alongside Composal’s browser verification.	Yes CodeQL builds a database of code and runs queries to find security vulnerabilities and correctness issues. Teams can use standard or custom queries.

Where each fits

Choose CodeQL when semantic queries, security scanning, or custom source analysis are needed. Choose Composal for hosted browser Scenarios, Discovery, and exploratory Findings tied to a live product.

Try this evaluation

Enable an appropriate CodeQL query set for a changed endpoint, then test the endpoint’s web flow in Composal. Compare source findings with runtime outcomes and retain each result for the audience it serves.

Coverage: Which user outcomes must this release prove, and which specialist checks must stay in your existing stack?
Setup: Who prepares accounts, test data, permissions and access to the deployment being tested?
Evidence: Can the engineer reproduce a reported failure from the recording and steps, without asking the tester to investigate again?
Ownership: Who updates the checks when the product changes, and can the team review what a passing result actually proves?