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
pitfall
    Impact
      Clean code attribute
        1. Unnecessary parentheses should not be used for constructs

           Code Smell
        2. Assertions should not be made at the end of blocks expecting an exception

           Bug
        3. Class of caught exception should be defined

           Bug
        4. References used in "foreach" loops should be "unset"

           Bug
        5. Classes named like "Exception" should extend "Exception" or a subclass

           Code Smell
        6. Static members should be referenced with "static::"

           Bug
        7. Errors should not be silenced

           Bug
        8. References should not be passed to function calls

           Code Smell
        9. Boolean checks should not be inverted

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

           Bug
        11. "switch" statements should not be nested

           Code Smell
        12. Deprecated constructor declarations should not be used

           Code Smell
        13. Deprecated predefined variables should not be used

           Code Smell
        14. Octal values should not be used

           Code Smell
        15. "for" loop stop conditions should be invariant

           Code Smell
        16. Control structures should use curly braces

           Code Smell
        17. Local variables should not have the same name as class fields

           Code Smell

        Deprecated constructor declarations should not be used

        consistency - conventional
        maintainability
        Code Smell
        • pitfall

        Why is this an issue?

        More Info

        Using a function in PHP with the same name as the nesting class was historically used to declare a class constructor. However, as of PHP 8.0.0, this declaration is discouraged and will provoke an E_DEPRECATED error, albeit it functions as a constructor.

        Instead, users should explicitly define the constructor by declaring a __construct(...) function. However, if both styles are present in the same class, PHP will treat the __construct function as the class constructor, which can cause unintended behavior.

        Adhering to this convention improves readability and maintainability by ensuring that the constructor declaration is named uniformly throughout the codebase.

        Noncompliant code example

        class Foo {
          function Foo() {...}
        }
        

        Compliant solution

        class Foo {
          function __construct() {...}
        }
        
          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