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: 10 rules found
redundant
    Impact
      Clean code attribute
        1. Null checks should not be used with "instanceof"

           Code Smell
        2. Assignments should not be redundant

           Code Smell
        3. "close()" calls should not be redundant

           Code Smell
        4. Jump statements should not be redundant

           Code Smell
        5. Nested "enum"s should not be declared static

           Code Smell
        6. Boolean expressions should not be gratuitous

           Code Smell
        7. Simple class names should be used

           Code Smell
        8. Redundant casts should not be used

           Code Smell
        9. Overriding methods should do more than simply call the same method in the super class

           Code Smell
        10. Exceptions in "throws" clauses should not be superfluous

           Code Smell

        Null checks should not be used with "instanceof"

        intentionality - clear
        maintainability
        Code Smell
        • redundant

        Why is this an issue?

        There’s no need to null test in conjunction with an instanceof test. null is not an instanceof anything, so a null check is redundant.

        Noncompliant code example

        if (x != null && x instanceof MyClass) { ... }  // Noncompliant
        
        if (x == null || ! x instanceof MyClass) { ... } // Noncompliant
        

        Compliant solution

        if (x instanceof MyClass) { ... }
        
        if (! x instanceof MyClass) { ... }
        
          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