SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • ShellShell
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
Java

Java static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your JAVA code

  • All rules 733
  • Vulnerability60
  • Bug175
  • Security Hotspot40
  • Code Smell458

  • Quick Fix 65
Filtered: 21 rules found
brain-overload
    Impact
      Clean code attribute
        1. Cognitive Complexity of methods should not be too high

           Code Smell
        2. Classes should not have too many "static" imports

           Code Smell
        3. Inner classes should not have too many lines of code

           Code Smell
        4. Files should contain only one top-level class or interface each

           Code Smell
        5. Variables should not be declared before they are relevant

           Code Smell
        6. Classes should not have too many fields

           Code Smell
        7. The ternary operator should not be used

           Code Smell
        8. A field should not duplicate the name of its containing class

           Code Smell
        9. Methods should not be too complex

           Code Smell
        10. "switch" statements should not have too many "case" clauses

           Code Smell
        11. Classes should not have too many methods

           Code Smell
        12. Methods should not have too many lines

           Code Smell
        13. Loops should not contain more than a single "break" or "continue" statement

           Code Smell
        14. Control flow statements "if", "for", "while", "switch" and "try" should not be nested too deeply

           Code Smell
        15. Classes should not be coupled to too many other classes

           Code Smell
        16. "switch case" clauses should not have too many lines of code

           Code Smell
        17. Methods should not have too many return statements

           Code Smell
        18. Magic numbers should not be used

           Code Smell
        19. Methods should not have too many parameters

           Code Smell
        20. Expressions should not be too complex

           Code Smell
        21. Files should not have too many lines of code

           Code Smell

        Methods should not have too many return statements

        intentionality - clear
        maintainability
        Code Smell
        • brain-overload

        Why is this an issue?

        Having too many return statements in a method increases the method’s essential complexity because the flow of execution is broken each time a return statement is encountered. This makes it harder to read and understand the logic of the method.

        Noncompliant code example

        With the default threshold of 3:

        public boolean myMethod() { // Noncompliant; there are 4 return statements
          if (condition1) {
            return true;
          } else {
            if (condition2) {
              return false;
            } else {
              return true;
            }
          }
          return false;
        }
        
          Available In:
        • SonarQube IdeCatch issues on the fly,
          in your IDE
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube Community BuildAnalyze code in your
          on-premise CI
          Available Since
          9.1
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Developer Edition
          Available Since
          9.1

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use