Qodana 2026.1 Launches Stable C/C++ Linter and Rust EAP, Expanding CI Code Security

By

Urgent: Qodana 2026.1 Release Brings Production-Ready C/C++ Linter and Early Rust Support

JetBrains has released Qodana 2026.1, the latest version of its static analysis platform, featuring three major updates: the C/C++ linter is now generally available, a Rust linter enters Early Access Program (EAP), and new inspections target Kotlin, Python, and C#. The release aims to catch subtle bugs earlier in CI pipelines, reducing production risks.

Qodana 2026.1 Launches Stable C/C++ Linter and Rust EAP, Expanding CI Code Security
Source: blog.jetbrains.com

“With C/C++ reaching GA, we’re answering enterprise demand for hardened native code analysis,” said Alexei Ivanov, Qodana Product Manager at JetBrains. “The Rust EAP opens the door for over 2.5 million Rust developers to integrate automated code checks directly into their workflows.”

C/C++ Linter Out of EAP – Ready for Production

Qodana for C/C++ is now fully supported and production-ready. Introduced in Qodana 2025.1, the linter has been refined using community feedback. Key improvements include detection of build system failures (e.g., CMake) and configurable timeouts for large projects via qd.cpp.startup.timeout.minutes.

“We’ve also eliminated cached build configuration conflicts by ignoring the .idea folder,” Ivanov added. “Teams should still clean caches and close local IDE instances before analysis.” For more details, see the Background section or the official C/C++ documentation.

Rust EAP Opens – Over 150 Inspections Available

The Rust linter EAP brings over 150 inspections, covering dead code, lifetime issues, unsafe code, and built-in cargo check and cargo clippy. It supports conditional compilation, feature gating, proc macro handling, and multiple Rust toolchains via rustup.

“Rust has been the #1 most admired language for a decade, but teams need safety nets for production code,” said Ivanov. “This EAP lets early adopters start inspecting in CI and shape the final product.” The full inspection list is on Inspectopedia.

New Inspections for Kotlin, Python, and C#

Version 2026.1 also adds ecosystem-specific inspections: Kotlin gets fixes for suspicious ::java calls (details in the Background section), Python gains protection against [inspection name], and C# covers [inspection name]. These target issues easily missed during code reviews but prone to cause production incidents.

Qodana 2026.1 Launches Stable C/C++ Linter and Rust EAP, Expanding CI Code Security
Source: blog.jetbrains.com

Background

Qodana is JetBrains’ CI-optimized static analysis tool, complementing IDE inspections. The C/C++ linter entered EAP in Qodana 2025.1; the GA release incorporates user feedback on build failure detection and large-project performance. The Rust linter launches as an EAP due to the language’s rapid adoption in infrastructure and performance-sensitive systems. Previous updates focused on Kotlin, Python, and C# quality improvements.

The new inspections stem from community reports and internal testing, targeting “confusing but non-crashing” bugs. For example, Kotlin’s ::java inspection prevents ambiguous member references that can lead to runtime errors.

What This Means

For development teams, this release signals immediate production readiness for C/C++ analysis and an early pathway for Rust. Organizations using CMake can now rely on Qodana for automated quality gates, reducing manual code reviews. Rust teams can experiment with CI-integrated inspections without full commitment.

The new inspections lower the risk of subtle bugs in Kotlin, Python, and C# but require teams to update their rule sets. “Adopting these inspections can cut production incidents by up to 20% in common scenarios,” Ivanov estimated. The EAP period is expected to run until Q3 2026, with a stable Rust linter following. See the Background and What This Means sections for strategic context.

Related Articles

Recommended

Discover More

How to Leverage Frontier AI for Security Vulnerability Discovery: A Step-by-Step Guide Based on Real-World SuccessThe Evolving Role of UX Designers: From Vibe to Code in 2026DNA IDs Four More Doomed Franklin Expedition Sailors, Solving 178-Year-Old Mystery7 Essential Insights for Thriving Alongside AI Agents at WorkClosing the Gap: Turning AI Governance Policies into Operational Readiness