Must-share information (formatted with Markdown):
- which versions are you using (SonarQube Server / Community Build, Scanner, Plugin, and any relevant extension) - v2025.4.2
- how is SonarQube deployed: zip, Docker, Helm - Docker
- what are you trying to achieve - to know the difference of rust rules in sonarqube vs rust clippy[ official linter]
- what have you tried so far to achieve this - to know the rules difference
Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!
Difference in Rule Count:
-
sonarqube Rust Quality Profile: 78 rules enabled by default in sonar wayBuilt-in,
-
Rust Clippy (official linter): 790+ lints/rules.
Could you please tell us more on what type of rules enabled by default ? how this will be impacted in good way for quality rules ?
where as offical linter is having more rules set
Hi, @vinayrangaswamy
First, let me apologize for taking so long to answer.
Second, we first included a selection of rules that match existing Sonar rules in other languages (rules with a key below 7000 generally), or are Clippy-specific and enabled by default in Clippy (rules with a key above 7000).
It takes time and energy to review and evaluate the rules and to add the level of information we provide in SonarQube, which is why we had to make a selection.
While we want to keep on adding rules to our Rust analyzer, this has to be balanced with other development activities which have more priority at this moment. If this topic is important to you, I will gladly have a chat with you on the subject to understand which type of rules would help you the most.
You can also vote or submit ideas on our public roadmaps for SonarQube Server and SonarQube Cloud, which will help raise the importance of the topics you care about.
In any case, I thank you for your interest and appreciate any feedback, so don’t hesitate to send me a direct message if you wish to have a conversation!
Denis Troller