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: 5 rules found
error-handling
    Impact
      Clean code attribute
        1. Delivering code in production with debug features activated is security-sensitive

           Security Hotspot
        2. Exceptions should not be created without being thrown

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

           Code Smell
        4. Classes named like "Exception" should extend "Exception" or a subclass

           Code Smell
        5. Generic exceptions ErrorException, RuntimeException and Exception should not be thrown

           Code Smell

        Classes named like "Exception" should extend "Exception" or a subclass

        consistency - identifiable
        maintainability
        Code Smell
        • convention
        • error-handling
        • pitfall

        Why is this an issue?

        Clear, communicative naming is important in code. It helps maintainers and API users understand the intentions for and uses of a unit of code. Using "exception" in the name of a class that does not extend Exception or one of its subclasses is a clear violation of the expectation that a class' name will indicate what it is and/or does.

        Noncompliant code example

        class FruitException {  // Noncompliant; this has nothing to do with Exception
          private $expected;
          private $unusualCharacteristics;
          private $appropriateForCommercialExploitation;
          // ...
        }
        
        class CarException {  // Noncompliant; the extends clause was forgotten?
          public function __construct(string message, Throwable cause) {
          // ...
        

        Compliant solution

        class FruitSport {
          private $expected;
          private $unusualCharacteristics;
          private $appropriateForCommercialExploitation;
          // ...
        }
        
        class CarException extends Exception {
          public function __construct(string message, Throwable cause) {
          // ...
        
          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