CodeQL Adds Rust and Build-Free C/C++ Scanning in General Availability
Allison details GitHub’s release of CodeQL support for Rust and build-free C/C++ scanning, enabling faster, more accessible security analysis for developers.
CodeQL Adds Rust and Build-Free C/C++ Scanning in General Availability
GitHub has announced that CodeQL—the engine behind GitHub code scanning—now generally supports Rust and build-free C/C++ project analysis. This marks the end of their public preview periods for both features, enabling security-focused development teams to identify vulnerabilities more efficiently.
Rust Support
- General availability: Rust joins C/C++, Java/Kotlin, JS/TS, Python, Ruby, C#, Go, GitHub Actions, and Swift as supported languages.
- Security coverage: The analysis addresses the OWASP Top 10 categories (except A06:2021-Vulnerable and Outdated Components, which uses Dependabot).
- Setup flexibility: Both default setup and advanced setup are supported.
- Autofix: Integration with Copilot Autofix offers automated fix recommendations based on scan results.
- Query Documentation: A detailed list of security queries for Rust is available in the CodeQL documentation.
Build-Free C/C++ Scanning
- General availability: CodeQL can now scan C/C++ codebases without requiring project builds.
- Preview results: During preview, over 10,000 repositories adopted the feature, achieving over 70% success rates with minimal manual setup.
- Operation: Build mode none is now standard in default setup for C/C++.
- Impact: This shift has substantially accelerated adoption, with one customer enabling security scans across 1,400+ repositories in under two days. Previously, this would have taken much longer.
Availability
- Available on github.com, CodeQL CLI
2.23.3
, and GitHub Enterprise Server from version 3.20.
Key Takeaways
- Security scanning is more accessible for Rust and C/C++ developers.
- Teams can onboard large codebases to security workflows with minimal friction.
- Support for automated fixes via Copilot Autofix speeds up time to remediation.
For further details and setup guides, see the GitHub Blog announcement.
This post appeared first on “The GitHub Blog”. Read the entire article here