Mission critical profile lacks many rules in Sonar Way profile

SonarQube Server / Community Build
,
1

I’m currently working with Enterprise Edition v2025.1.1 and attempting to identify the quality profile which best makes sense to use for our C++ project.

When doing so, I elected to compare the “Mission critical” profile with the “Sonar way” profile. I was expecting to see the Mission critical profile be a superset of the Sonar way, possibly with a few minor changes where less-strict rules were replaced with more strict rules.

Instead, I was surprised to see that:
“Mission critical has 58 additional rules and 62 fewer rules than Sonar way.”

Why are there rules present in the “Sonar way” profile not present in the “Mission critical” profile? For example, the rule of “Single-bit named bit fields should not be of a signed type”. There are many others which lack comparable rules (notwithstanding the confusion between similar rules such as cpp:S859 vs cpp:M23_090).

5

Hello @garrettkajmowicz,

Sorry for the delay in answering, I missed your post.

The idea behind Mission Critical is indeed to contain all of Sonar Way, plus specific mission-critical rules, minus rules in SonarWay that are redundant with the mission-critical rules.

However, we are also in the process of adding rules that cover all of MISRA C++:2023. If you are interested in mission-critical rules, you should probably look is them. They are currently provided in early access, and you need to opt-in into these rules (see here more more details).

Until we are done with supporting MISRA C++:2023, we decided to freeze the Mission Critical project, because we’ll need to revisit it at that time. Which is why there might be rules in SonarWay not yet reflected in Mission Critical.

Can I do something more to help you?