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: 3 rules found
performance
    Impact
      Clean code attribute
        1. `str_replace` should be preferred to `preg_replace`

           Code Smell
        2. "php_sapi_name()" should not be used

           Code Smell
        3. References should not be passed to function calls

           Code Smell

        `str_replace` should be preferred to `preg_replace`

        intentionality - efficient
        maintainability
        Code Smell
        • regex
        • performance

        Why is this an issue?

        An preg_replace call always performs an evaluation of the first argument as a regular expression, even if no regular expression features were used. This has a significant performance cost and therefore should be used with care.

        When preg_replace is used, the first argument should be a real regular expression. If it’s not the case, str_replace does exactly the same thing as preg_replace without the performance drawback of the regex.

        This rule raises an issue for each preg_replace used with a simple string as first argument which doesn’t contains special regex character or pattern.

        Noncompliant code example

        $str = "Bob is a Bird... Bob is a Plane... Bob is Superman!";
        $changed = preg_replace("/Bob is/", "It's", $str); // Noncompliant
        $changed = preg_replace("/\.\.\./", ";", $changed); // Noncompliant
        

        Compliant solution

        $str = "Bob is a Bird... Bob is a Plane... Bob is Superman!";
        $changed = str_replace("Bob is", "It's", $str);
        $changed = str_replace("...", ";", $changed);
        

        Or, with a regex:

        $str = "Bob is a Bird... Bob is a Plane... Bob is Superman!";
        $changed = preg_replace("/\w*\sis/", "It's", $str);
        $changed = preg_replace("/\.{3}/", ";", $changed);
        
          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