MISRA C &
MISRA C++

Every MISRA Edition.
Same Toolchain.

Whether your project targets the 2004 / 2012 / 2023 cadence of MISRA C, or the 2008 / 2023 cadence of MISRA C++, the YerraSAST C and C++ scanners read the project's declared MISRA target and emit findings tagged with the correct rule ID and decidability category for that edition. No flag-juggling, no separate runs.

Counts above reflect the published MISRA rule tables. PhantomYerra natively detects the rules listed; Mandatory and Required rules are covered at 100% for editions 2012 onward. Advisory rules with low decidability (i.e. requiring human judgement) are emitted as advisories with a confidence tier set on the finding so the operator can triage them with their own SME review.

How A Finding Lands.

Three representative MISRA C:2023 rules - one Mandatory, one Required, one Advisory - to show how PhantomYerra emits findings, what the evidence looks like, and how the report maps each one back to the MISRA clause.

/* Vulnerable: x is read before assignment on the if-false path. */
int compute(int flag) {
    int x;
    if (flag) { x = 42; }
    return x;  /* MISRA C:2023 Rule 9.1 - Mandatory - read before set */
}

size_t factorial(size_t n) {
    if (n <= 1) return 1;
    return n * factorial(n - 1);  /* MISRA C:2023 Rule 17.2 - direct recursion */
}

/* In header: */
#define MAX 100

/* In source - Rule 5.5 violation: */
int compute(int MAX) {  /* parameter shadows macro */
    return MAX * 2;
}

From Scan to Sign-Off.

A MISRA-compliant build is more than a passing scan - it's a documented deviation register, signed-off compliance certificate, and an audit trail. PhantomYerra produces all three from a single workspace.

More Coverage.
Same Platform.