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
Apex

Apex static code analysis

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

  • All rules 56
  • Vulnerability1
  • Bug12
  • Security Hotspot3
  • Code Smell40
Filtered: 6 rules found
cwe
    Impact
      Clean code attribute
        1. Hard-coded credentials are security-sensitive

           Security Hotspot
        2. All code should be reachable

           Bug
        3. "switch" statements should have "when else" clauses

           Code Smell
        4. Useless "if(true) {...}" and "if(false){...}" blocks should be removed

           Bug
        5. Track uses of "TODO" tags

           Code Smell
        6. Track uses of "FIXME" tags

           Code Smell

        All code should be reachable

        intentionality - logical
        reliability
        Bug
        • cwe
        • unused

        Once control flow has been moved out of the current code block, any subsequent statements become effectively unreachable.

        Why is this an issue?

        More Info

        Jump statements (return, break, continue) and throw expressions move control flow out of the current code block. So any statements that come after a jump are dead code.

        Noncompliant code example

        Integer foo(Integer a) {
            Integer i = 10;
            return i + a; // Noncompliant
            i++; // dead code
        }
        

        Compliant solution

        Integer foo(Integer a) {
            Integer i = 10;
            return i + a; // Noncompliant
        }
        
          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 ServerAnalyze code in your
          on-premise CI
          Enterprise
          Edition
          Available Since
          9.1

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use