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
PHP

PHP static code analysis

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

  • All rules 273
  • Vulnerability42
  • Bug51
  • Security Hotspot34
  • Code Smell146
Filtered: 17 rules found
unused
    Impact
      Clean code attribute
        1. Non-empty statements should change control flow or have at least one side-effect

           Bug
        2. Test methods should be discoverable

           Code Smell
        3. A subclass should not be in the same "catch" clause as a parent class

           Code Smell
        4. Caught Exceptions must derive from Throwable

           Bug
        5. "catch" clauses should do more than rethrow

           Code Smell
        6. TestCases should contain tests

           Code Smell
        7. Values should not be uselessly incremented

           Bug
        8. Related "if/else if" statements and "cases" in a "switch" should not have the same condition

           Bug
        9. Unused assignments should be removed

           Code Smell
        10. All code should be reachable

           Bug
        11. Unused local variables should be removed

           Code Smell
        12. Sections of code should not be commented out

           Code Smell
        13. Unused function parameters should be removed

           Code Smell
        14. Unused "private" methods should be removed

           Code Smell
        15. Empty statements should be removed

           Code Smell
        16. Unused "private" fields should be removed

           Code Smell
        17. All "catch" blocks should be able to catch exceptions

           Bug

        Related "if/else if" statements and "cases" in a "switch" should not have the same condition

        intentionality - logical
        reliability
        Bug
        • unused
        • pitfall

        Why is this an issue?

        A switch and a chain of if/else if statements is evaluated from top to bottom. At most, only one branch will be executed: the first one with a condition that evaluates to true.

        Therefore, duplicating a condition automatically leads to dead code. Usually, this is due to a copy/paste error. At best, it’s simply dead code and at worst, it’s a bug that is likely to induce further bugs as the code is maintained, and obviously it could lead to unexpected behavior.

        For a switch, if the first case ends with a break, the second case will never be executed, rendering it dead code. Worse there is the risk in this situation that future maintenance will be done on the dead case, rather than on the one that’s actually used.

        On the other hand, if the first case does not end with a break, both cases will be executed, but future maintainers may not notice that.

        Noncompliant code example

        if ($param == 1)
          openWindow();
        else if ($param == 2)
          closeWindow();
        else if ($param == 1)  // Noncompliant
          moveWindowToTheBackground();
        
        
        switch($i) {
          case 1:
            //...
            break;
          case 3:
            //...
            break;
          case 1:  // Noncompliant
            //...
            break;
          default:
            // ...
            break;
        }
        

        Compliant solution

        if ($param == 1)
          openWindow();
        else if ($param == 2)
          closeWindow();
        else if ($param == 3)
          moveWindowToTheBackground();
        
        switch($i) {
          case 1:
            //...
            break;
          case 3:
            //...
            break;
          default:
            // ...
            break;
        }
        
          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