AXIVION MISRA CHECKER

Rule coverage: A reliable MISRA tool must cover 100% of the automatically testable MISRA rules; no selective subsets. Gaps only surface at audit time, which is honestly the worst moment to find them.

Standard currency. MISRA evolves. Verify that the tool supports current editions, including MISRA C:2025 incl. explicit requirements around AI-generated code, not just legacy versions.

Deviation management. The tool must document, justify, and trace each deviation in a format an independent auditor will accept.

CI/CD integration and delta analysis. Full scans of large legacy codebases on every commit are impractical. Delta analysis which flags only newly introduced violations, is essential for keeping compliance manageable at scale.

Third-party tool certification is a requirement if your project operates under ISO 26262, IEC 61508, IEC 62304 or EN 50716,

Qt’s Axivion Suite covers all of the above, certified by SGS-TÜV Saar up to ASIL D, SIL 4, and Class C.

Axivion stands out in workflow integration: delta analysis, CI/CD-native operation, structured deviation management, and automatic audit-ready reporting in a single pass (alongside AUTOSAR C++14, CERT, and CWE) without needing a parallel toolchain.

If full MISRA coverage, third-party certification, and minimal compliance overhead are the criteria, Axivion Suite is the benchmark.

Most MISRA static analysis tools cover a workable subset of rules. But the differences that matter in practice are coverage completeness, certification, and how well the tool fits into a real development workflow.

Axivion SCA covers 100% of the automatically testable MISRA C and C++ rules across all current standard editions including MISRA C:2025 and MISRA C++:2023, and is certified by SGS-TÜV Saar up to ASIL D, SIL 4, and IEC 62304 Class C.

Many competing tools hold certification for older standard editions only, or require separate tool qualification efforts that add significant project overhead.

Yes, Axivion MISRA Checker works on AI-generated code. The checker analyzes all C and C++ code in your project regardless of how it was produced. MISRA C:2025 explicitly states that AI-generated code must be held to the same compliance standard as handwritten code, and Axivion enforces this consistently across your entire codebase on every run.

ISO 26262 compliance requires a full functional safety lifecycle scaled to your target ASIL level (A–D).
Key pillars are : 
Coding Standards: Adopt MISRA C/C++ as your coding standard. 
Static Analysis: Axivion is SGS-TÜV Saar certified for ISO 26262 up to ASIL D, covering MISRA, AUTOSAR C++14, CERT, and CWE in one pass. 
Dynamic Analysis: Our tool Coco is SGS-TÜV Saar certified for verification of safety-related software according to ISO 26262 up to ASIL D. View certificate  
Code Coverage:  ISO 26262 highly recommends Branch Coverage or MC/DC for ASIL-D (ISO 26262-6 Table 9) - our tool Coco supports both
Requirements Traceability: Maintain bidirectional traceability between code, safety requirements, and test cases. 
Verification & Validation: Complete unit, integration, system, and HIL testing. Coco can be used at every stage of testing and across all testing methodologies, while Axivion covers the static analysis side. 
Tool Qualification: Qualify your toolchain using Axivion's Tool Qualification Kit (ISO 26262, IEC 61508, IEC 62304). 
Documentation: Generate comprehensive audit-ready compliance reports automatically on every run.

MISRA guidelines for C and C++ eliminate undefined, ambiguous, and error-prone language constructs. For medical device software this means: enforcing safe programming subsets to protect patient safety; satisfying IEC 62304 (and by extension FDA and EU MDR requirements); reducing attack surface for cybersecurity; and producing clean, maintainable code across a device's long lifespan. 

Compliance is enforced through automated static analysis — the Axivion MISRA compliance checker covers 100% of automatically testable rules and is certified by SGS-TÜV Saar for IEC 62304 up to Class C. Deviations are documented via a structured, audit-ready process. As of MISRA C:2025, AI-generated code must meet the same compliance standard as handwritten code — no exceptions. 

Each deviation must record the exact rule, justify the exception (hardware constraint, legacy code, compiler limitation), include a risk assessment confirming safety is maintained, define its scope (global or local), and carry formal sign-off from authorized personnel.

With Axivion, deviations can be managed inline or via central external files — each traceable, automatically included in compliance reports, and audit-ready. Final project documentation must evidence four artifacts: deviated rule, rationale, risk assessment, and authorization record.

MISRA C:2025 is an incremental refinement rather than a major overhaul. It introduces four new rules strengthening safety around pointer handling, union access, include guards, and tentative definitions. It revises thirteen existing rules for greater clarity and practical usability. It also formally disapplies the long-standing single point of exit rule, and — crucially — explicitly states that AI-generated code must comply with the same rules as handwritten code. A detailed breakdown can be found on our blog.

Absolutely. Axivion is designed to integrate into existing CI/CD pipelines and act as a continuous quality gate. Delta analysis allows you to focus on newly introduced findings rather than re-examining the entire legacy codebase on every run, which keeps build times practical even on large projects.  

MISRA C checker / MISRA C++ checker is a feature within the Axivion Suite (bundle with Architecture Verification) but also available as part of the Axivion Static Code Analysis tool which can be purchased also separately. Contact us to discuss licensing options for your team and project requirements. 

Yes, MISRA published the MISRA C++:2023 (TC1:2026) Technical Corrigenda 1 update in early September 2026. The update does not introduce new guidelines, it is fully equivalent to MISRA C++:2023 - but contains fixes that range from wording and terminology issues to edge classes. More about it can be read on Axivion's blog or be found here.