Perforce adds Rust static analysis to QAC and Klocwork release

Perforce has pushed Rust deeper into the world of safety-critical tooling, adding language support for Rust in its 2026.1 release of QAC and Klocwork. The move matters because these are not developer toys or general-purpose linters. They are static-analysis products used in embedded development, where aerospace, automotive, and medical-device teams care as much about traceability and auditability as they do about speed.

The company said QAC and Klocwork now provide cross-language support for Rust, C, and C++, a practical step for organizations that live in mixed-language codebases and cannot simply rewrite everything at once. Klocwork 2026.1 also introduced early-access support for Rust projects, including native Rust checkers and integrated Clippy support. Perforce says the tools are aimed at catching defects before deployment, including problems that may surface in Rust code written by a person or assisted by AI.

That framing goes to the heart of why this release is notable. Rust has already won credibility on memory safety, but Perforce is positioning static analysis as the next layer of assurance for teams that still need to prove correctness, not just avoid use-after-free bugs. The company said its Rust analysis covers inter-procedural dataflow, unsafe block analysis, and cross-language coverage in mixed Rust/C/C++ systems, areas where common linters can leave blind spots. It also said the tools provide auditable reporting intended to support regulated audits.

The timing lines up with a broader shift in the Rust ecosystem. The Rust Foundation and its partners launched the Safety-Critical Rust Consortium in June 2024, with members including AdaCore, Arm, Ferrous Systems, HighTec EDV-Systeme GmbH, Lynx Software Technologies, OxidOS, TECHFUND, TrustInSoft, Veecle, and Woven by Toyota. The Rust Project’s 2026 safety-critical roadmap is also moving toward MC/DC coverage support in rustc, normative guidance for unsafe Rust, and a dedicated place for safety-critical lints in Clippy.

Perforce has also been looking at the market from the automotive side. Its 2026 Automotive Software Development Report surveyed 450 automotive development professionals and was released in March 2026, reinforcing the same message: modern toolchains are becoming a competitiveness issue as software-defined vehicles, AI workflows, and compliance pressure all rise at once. For Rust, the significance is clear. The language is no longer just winning minds on safety alone. It is now being wired into the verification stack that regulated industries already trust.