Helix QAC 2025.2 refers to the 2025 release series of Perforce QAC (formerly known as Helix QAC), a leading static code analysis tool for C and C++ developed by Perforce Software. Originally launched in 1986 as QA·C by Programming Research Ltd. (PRQA), it was rebranded under the Helix umbrella after Perforce’s acquisition and fully transitioned to the Perforce QAC name starting in 2025.2. This tool is widely used in safety-critical and regulated industries like automotive, aerospace, medical devices, and nuclear, where it enforces coding standards (e.g., MISRA, AUTOSAR) and functional safety norms (e.g., ISO 26262, IEC 61508). It’s certified by TÜV SÜD for these standards and holds ISO 9001 | TickIT plus certification.

The 2025 releases emphasize enhanced compliance, CI/CD integration, and deprecations for legacy features, building on the 2024 versions with deeper analysis accuracy and broader standards support. As of September 2025, the latest is 2025.3, with ongoing updates for performance and usability.

Key New Features and Improvements in Helix QAC 2025.2 Releases

  • MISRA C:2025 Compliance (2025.1): Full 100% coverage of the newly published MISRA C:2025 guidelines via a dedicated compliance module, enabling early detection of deviations in embedded C code.
  • Expanded CERT C Coverage (2025.1): Increased support for CERT C Level 1 recommendations, focusing on secure coding practices to mitigate vulnerabilities like buffer overflows and memory issues.
  • Rebranding and UI Updates (2025.2): Complete shift to “Perforce QAC” branding, including new logos, installers, and documentation. Installation directories changed from ‘Helix-QAC-[version]’ to ‘QAC-[version]’. User interfaces and tools reflect this for consistency.
  • Licensing Changes for Perforce Validate Integration (2025.1+): New server build licenses required for CI/CD analysis and uploads to Perforce Validate (a centralized repository for QAC and Klocwork results). Commands like qacli validate build or qacli validate cibuild are now mandatory for automated workflows; plugin-based analysis in Eclipse/Visual Studio is limited for certain features.
  • Deprecated Features:
    • Output types DIAGLIST, ANNSRC, and SARIF for qacli view (deprecated in 2025.1, removal planned for 2026.1).
    • Helix_Generic_C and Helix_Generic_C++ Checker Configuration Tables (CCTs) replaced with QAC_Generic_C and QAC_Generic_C++.
    • From 2025.3: Eclipse and Visual Studio plugins lose configuration/initiation for CMA (Code Model Analyzer) solutions; use GUI/CLI instead. CMA icons removed from toolbar but accessible via menus.
  • CLI and Plugin Enhancements: Improved qacli commands for validation and builds, with better support for large-scale codebases (millions of lines). Integrations with IDEs like Visual Studio, Eclipse, and CI tools (Jenkins, Jira) are streamlined, plus new compiler support for multi-compiler projects.
  • Performance and Accuracy: Enhanced defect prioritization using filters, suppressions, and baselines to focus on high-risk issues. Actionable diagnostics help fix critical bugs early, reducing development costs.

Compatibility and Usage Notes

  • Supported Platforms: Windows, Linux, and macOS (64-bit), with broad compiler compatibility (GCC, Clang, MSVC, IAR, etc.). Requires Reprise License Manager (RLM) v16.1BL1 or later for 2025.1+.
  • Backward Compatibility: Models and configurations from prior versions (e.g., 2024.x) can be imported, but deprecated CCTs and outputs may need updates. Test large projects in the new environment.
  • Integrations: Seamless with Perforce tools (Helix Core for version control, Klocwork), CI/CD pipelines, and third-party IDEs/IDEs like Unity/Unreal Engine. No direct Autodesk integration noted, though it supports general C/C++ workflows.
  • Downloads and Licensing: Available via Perforce’s customer portal for licensed users. Free trials are offered; contact Perforce for demos. Pricing is subscription-based (not publicly detailed), tailored for enterprise use.
  • API/Scripting: Updated CLI for automation; Python/VBScript examples available in documentation.