Overview
Overview
SonarQube Community Build executes rules on source code to generate issues. The way rules are categorized depends on the mode your instance of SonarQube Community Build is using.
In Multi-Quality Rule (MQR) mode, rules are categorized by software qualities: security, reliability, and maintainability. A rule may impact more than one software quality.
Under maintainability and reliability, zero false positives are expected. At least this is the target so that developers don't have to wonder if a fix is required.
For vulnerabilities, the goal is to have more than 80% of issues be true positives.
Security hotspot rules draw attention to security-sensitive code. After being reviewed by a developer, more than 80% of issues are expected to be quickly resolved as "reviewed."
The Sonar Rules catalog is the entry point where you can discover all the existing rules or create new ones based on available templates.
There are four types of rules:
- Code smell (maintainability domain)
- Bug (reliability domain)
- Vulnerability (security domain)
- Security hotspot (security domain)
For code smells and bugs, zero false positives are expected. At least this is the target so that developers don't have to wonder if a fix is required.
For vulnerabilities, the goal is to have more than 80% of issues be true positives.
Security hotspot rules draw attention to security-sensitive code. After being reviewed by a developer, more than 80% of issues are expected to be quickly resolved as "reviewed."
The Sonar Rules catalog is the entry point where you can discover all the existing rules or create new ones based on available templates.
Rules
By default, when selecting the top menu item Rules, you will see all the available rules installed on your SonarQube Community Build instance. You have the ability to review and narrow the selection based on search criteria in the left sidebar:
- Language: the language to which a rule applies.
- Software Quality: security, reliability, maintainability bug
- Security hotspot: security hotspot rules.
- Default Severity: the severity of all the software qualities it has an impact on.
- Tag: it is possible to add tags to rules in order to classify them and to help discover them more easily.
- Clean Code attributes: consistency, intentionality, adaptability, responsibility
- Repository: the engine/analyzer that contributes rules to SonarQube Community Build.
- Status: rules can have 3 different statuses:
- Beta: The rule has been recently implemented and we haven't gotten enough feedback from users yet, so there may be false positives or false negatives.
- Deprecated: The rule should no longer be used because a similar, but more powerful and accurate rule exists.
- Ready: The rule is ready to be used in production.
- Available since: the date when a rule was first added on SonarQube Community Build. This is useful to list all the new rules since the last upgrade of a plugin for instance.
- Template: display rule templates that allow you to create custom rules (see Custom rules below on this page).
- Quality profile: inclusion in or exclusion from a specific profile
If a Quality profile is selected, it is also possible to check for its active severity and whether it is inherited or not. See the Quality profiles documentation for more.
By default, when selecting the top menu item Rules, you will see all the available rules installed on your SonarQube Community Build instance. You have the ability to review and narrow the selection based on search criteria in the left sidebar:
- Language: the language to which a rule applies.
- Type: bug, vulnerability, code smell, or security hotspot rules.
- Default Severity the original severity of the rule - as defined by SonarQube Community Build.
- Tag: it is possible to add tags to rules in order to classify them and to help discover them more easily.
- Repository: the engine/analyzer that contributes rules to SonarQube Community Build.
- Status: rules can have 3 different statuses:
- Beta: The rule has been recently implemented and we haven't gotten enough feedback from users yet, so there may be false positives or false negatives.
- Deprecated: The rule should no longer be used because a similar, but more powerful and accurate rule exists.
- Ready: The rule is ready to be used in production.
- Available since: the date when a rule was first added on SonarQube Community Build. This is useful to list all the new rules since the last upgrade of a plugin for instance.
- Template: display rule templates that allow you to create custom rules (see Custom rules below on this page).
- Quality profile: inclusion in or exclusion from a specific profile
If a Quality profile is selected, it is also possible to check for its active severity and whether it is inherited or not. See the Quality profiles documentation for more.
Rule details
To see the details of a rule, either click the rule with your mouse or use the right arrow key. Along with basic rule data, you'll also be able to see which, if any, profiles the rule is active in and how many open issues have been raised with it.
The following actions are available only if you have the correct permission level Administer quality profiles and gates:
- Add/Remove tags:
- It is possible to add existing tags on a rule, or to create new rules; simply enter a new name while typing in the text field.
- Note that some rules have built-in tags that you cannot remove. For example, the rules are provided by the plugins which contribute to the rules.
- Extend description:
- You can extend rule descriptions to let users know how your organization is using a particular rule or to give more insight into a rule.
- Note that the extension will be available to non-admin users as a normal part of the rule details.
Rule templates and custom rules
Rule templates are provided by plugins as a basis for users to define their own custom rules in SonarQube Community Build.
- To find templates, select the Show Templates Only option from the Template dropdown menu.
- Rule Template appears below the title indicating that this is a template.
- Click through the tabs for more information about the custom rule.
- Click Create to define your custom rule and enter the following information:
- Name: Enter a meaningful name for the rule.
- Key (auto-suggested)
- Type: The options are Issue or Security Hotspot, inherited by default from the template.
- Category: The options are Consistency, Intentionality, Adaptability, or Responsibility, which are inherited by default from the template.
- Attribute: The options are Conventional, Identifiable, or Formatted, which are inherited by default from the template.
- Software Quality: Select all that apply, the options are Security, Reliability, and Maintainability, inherited by default from the template.
- Severity: The options are Blocker, High, Medium, Low, or Info, inherited by default from the template.
- Status: The options are Ready, Beta, or Deprecated, inherited by default from the template.
- Description (Markdown format is supported): Write a meaningful description for your custom rule.
- The parameters specified by the template
- Name: Enter a meaningful name for the rule.
- Key (auto-suggested)
- Type: The options are Bug, Vulnerability, Code Smell, or Security Hotspot, inherited by default from the template.
- Severity: The options are Blocker, Critical, Major, Minor, or Info. The recommended severity level is inherited from the template.
- Status: The options are Ready, Beta, or Deprecated, inherited by default from the template.
- Description (Markdown format is supported): Write a meaningful description for your custom rule.
- The parameters specified by the template.
The Custom rules section contains a list of all custom rules created from the template. Click on the custom rule link to view details or Delete it from the system.
Custom rules
Custom rules are considered like any other rule, except that you can edit or delete them:
When deleting a custom rule, it is not physically removed from the SonarQube Community Build instance. Instead, its status is set to "REMOVED". This allows current or old issues related to this rule to be displayed properly in SonarQube Community Build until they are fully removed.
Extending coding rules
Custom coding rules can be added. See Adding coding rules for detailed information and tutorials.
Rule types and severities
When using Multi-Quality Rule mode, there are four categories: Security, reliability, maintainability, and security hotspots. Rules are assigned to one or more categories based on the answers to these questions:
Is the rule about code that could be exploited by an attacker?
If so, then it's a security rule.
Is the rule about code that is security-sensitive?
If so, then it's a security hotspot rule.
Is the rule about code that is demonstrably wrong, or more likely wrong than not?
If the answer is "yes", then it's a reliability rule.
Is the rule neither a bug nor a vulnerability?
If so, then it's a maintainability rule.
When using Standard Experience mode, there are four categories: Bugs, vulnerabilities, security hotspots, bugs, and code smells. Rules are assigned to categories based on the answers to these questions:
Is the rule about code that could be exploited by an attacker?
If so, then it's a vulnerability rule.
If not...
Is the rule about code that is security-sensitive?
If so, then it's a security hotspot rule.
If not...
Is the rule about code that is demonstrably wrong, or more likely wrong than not?
If the answer is "yes", then it's a bug rule.
If not...
Is the rule neither a bug nor a vulnerability?
If so, then it's a code smell rule.
Users with appropriate permissions are able to set a custom severity on a rule.
How severities are assigned
The table below lists the severity metrics used in Multi-Quality Rule mode.
| Severity | Definition |
|---|---|
| Blocker | Bug with a high probability to impact the behavior of the application in production. |
| High | Either a bug with a low probability of impacting the behavior of the application in production or an issue that represents a security flaw. |
| Medium | A quality flaw that can highly impact the developer's productivity. |
| Low | A quality flaw that can slightly impact the developer's productivity. |
| Info | Neither a bug nor a quality flaw, just a finding. |
The table below lists the severity metrics used in Standard Experience mode.
| Severity | Definition |
|---|---|
| Blocker | Bug with a high probability to impact the behavior of the application in production. For example, a memory leak, or an unclosed JDBC connection are BLOCKERs that must be fixed immediately. |
| Critical | Either a bug with a low probability to impact the behavior of the application in production or an issue that represents a security flaw. An empty catch block or SQL injection would be a CRITICAL issue. The code must be reviewed immediately. |
| Major | A quality flaw that can highly impact the developer's productivity. An uncovered piece of code, duplicated blocks, or unused parameters are examples of MAJOR issues. |
| Minor | A quality flaw that can slightly impact the developer's productivity. For example, lines should not be too long, and "switch" statements should have at least 3 cases, are both be considered MINOR issues. |
| Info | Neither a bug nor a quality flaw, just a finding. |
To assign severity to a rule, we ask a further series of questions. The first one is basically:
What's the worst thing that could happen?
In answering this question, we try to factor in Murphy's Law without predicting Armageddon.
Then we assess whether the impact and likelihood of the worst thing (see the How severity and likelihood are decided section below) are high or low, and plug the answers into a truth table:
| Standard Experience | MQR mode | Impact | Likelihood |
| Blocker | Blocker | ✅ | ✅ |
| Critical | High | ✅ | ❌ |
| Major | Medium | ❌ | ✅ |
| Minor | Low | ❌ | ❌ |
How severity and likelihood are decided
To assess the severity of a rule, we start from the worst thing (see the How severities are assigned section above) and ask category-specific questions.
Reliability
Impact: Could the worst thing cause the application to crash or corrupt stored data?
Likelihood: What's the probability that the worst thing will happen?
Security
Impact: Could the exploitation of the worst thing result in significant damage to your assets or your users?
Likelihood: What is the probability that an attacker will be able to exploit the worst thing?
Security hotspots
Security hotspots are not assigned severities as it is unknown whether there is truly an underlying vulnerability until they are reviewed.
Bugs
Impact: Could the worst thing cause the application to crash or corrupt stored data?
Likelihood: What's the probability that the worst thing will happen?
Vulnerabilities
Impact: Could the exploitation of the worst thing result in significant damage to your assets or your users?
Likelihood: What is the probability that an attacker will be able to exploit the worst thing?
Security hotspots
Security hotspots are not assigned severities as it is unknown whether there is truly an underlying vulnerability until they are reviewed.
What might change after a software update
Sonar developers continually re-evaluate our rules to provide the best results. This process is evident in each release and means some rule-specific properties may change after an upgrade, even in a custom Quality Profile. This is normal and expected, and is no cause for alarm. The following are rule-specific properties that may change in an upgrade:
- Software quality: Software quality (security, reliability, maintainability) updates to rules can occur. Changes to a rule's qualities will not be applied to issues previously raised by the rule until the project is reanalyzed.
- Type: Type (bug, vulnerability, code smell) updates happen on occasion. When a rule type is updated, its value will update automatically in every profile that uses it. Although the rule will be updated, issues previously raised by the rule will not be updated. For example, if a rule transitioned from bug to code smell, the existing issues will retain their original bug type, and new issues will get the new type, code smell.
- Severity: Changes to a rule's default severity will automatically be applied in quality profiles where the default severity was used. Although the rule will be updated, existing issues raised by the rule will not be updated. Note that it is possible to override a rule's default severity in a profile, and your custom override should remain intact in your quality profile after the upgrade.
- Tags: Two types of tags may be attached to a rule: the default tags that come out of the box, and the custom tags added by administrators. When the default tags attached to a rule are updated in SonarQube Community Build, those changes will happen automatically. Custom tags associated with a rule will not change.
- Key: Can change but this is uncommon. Typically this happens in the rare case that, for whatever reason, a key that was non-normal needs to be normalized. When the key of a rule is changed, related issues are updated as well, so that they remain related to the re-keyed rule.
- Status: Status does not affect the operation of a rule and has no impact on its issues. There are three possible rule statuses: beta, ready, and deprecated. Sometimes, rules are first issued in beta status and then moved to ready. Most rules are in ready status; ready to be used in production. When Sonar developers realize that a rule no longer makes sense, they first deprecate the rule, then eventually drop it.
For a comprehensive list of available rules and their up-to-date properties, see our Sonar Rules catalog.
Was this page helpful?
© 2008-2024 SonarSource SA. All rights reserved. SONAR, SONARSOURCE, SONARQUBE, and CLEAN AS YOU CODE are trademarks of SonarSource SA.
