Comment on page
CodeScan has a set of metadata rules; these rules allow you to scan your settings to ensure that your org is secure and clean.
CodeScan divides the rules into 4 categories:
- Bug (reliability domain)
- Vulnerability (security domain)
- Code smell (maintainability domain)
- Security hotspot (security domain)
For code smells and bugs, zero false positives are expected.
For vulnerabilities, the goal is to have more than 80% of issues be true positives.
Security hotspot rules draw attention to code that is security-sensitive. It is expected that more than 80% of the issues will be quickly resolved as "reviewed" after being reviewed by a developer.
You can access the Quality Rules page from the Organization’s home page.
By default, you will see all the available rules installed on your CodeScan 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.
- 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 CodeScan.
- Default Severity: Filter Quality Rules based on the severity of the rule
- 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 CodeScan. This is useful to list all the new rules since the last upgrade of a plugin, for instance.
- Template: display the rules created from a template.
- Quality profile: inclusion in or exclusion from a specific profile
Click on the rule to see the details of a rule. 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.
For each rule, you can:
- Add or remove existing tags on a rule
- 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.
To make changes to the Quality Rules, users must be granted the Administer Quality Gates or Profile permission.
Custom rules are considered like any other rule, except that you can edit or delete them. You can define your own custom rules in CodeScan using Rule templates. To find templates, select the Show Templates Only option from the Template dropdown menu.
To create a custom rule from a template, select Create next to the Custom rules heading and enter the following information:
- Key (auto-suggested)
- Description (Markdown format is supported)
- The parameters specified by the template
Unlike other rules, you can edit or delete custom rules. When a custom rule is deleted, it is not removed from the CodeScan Cloud instance. Instead, its status is set to "REMOVED", allowing relevant issues to continue to be displayed properly.
Click on the custom rules to view its details. Under the Parameter section, you have the option to edit the custom rule information or delete them.