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

        Unused "private" methods should be removed

        intentionality - clear
        maintainability
        Code Smell
        • unused

        This rule raises an issue when a private function is never referenced in the code.

        Why is this an issue?

        A function that is never called is dead code, and should be removed. Cleaning out dead code decreases the size of the maintained codebase, making it easier to understand the program and preventing bugs from being introduced.

        This rule detects functions that are never referenced from inside a translation unit, and cannot be referenced from the outside.

        It also raises on unused protected functions in PHP enumerations. In PHP enumerations private and protected are equivalent because inheritance is not allowed.

        Code examples

        Noncompliant code example

        class Foo {
          private function __construct() {}   // Compliant, private empty constructor intentionally used to prevent any direct instantiation of a class.
        
          public static function doSomething() {
            $foo = new Foo();
            ...
          }
        
          private function unusedPrivateFunction() {}  // Noncompliant
        }
        
        enum ExampleEnum {
          case FIRST_CASE;
        
          private function unusedPrivateFunction() {} // Noncompliant
          protected function unusedProtectedFunction() {} // Noncompliant
        }
        

        Compliant solution

        class Foo {
          private function __construct() {}   // Compliant, private empty constructor intentionally used to prevent any direct instantiation of a class.
        
          public static function doSomething() {
            $foo = new Foo();
          }
        }
        
          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