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
C++

C++ static code analysis

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

  • All rules 674
  • Vulnerability13
  • Bug139
  • Security Hotspot19
  • Code Smell503

  • Quick Fix 91
Filtered: 25 rules found
brain-overload
    Impact
      Clean code attribute
        1. The global namespace should only contain "main", namespace declarations, and "extern" C declarations

           Code Smell
        2. "#undef" should be used with caution

           Code Smell
        3. Object declarations should contain no more than 2 levels of pointer indirection

           Code Smell
        4. "goto" statement should not be used

           Code Smell
        5. "[[nodiscard]]" attributes on types should include explanations

           Code Smell
        6. Cognitive Complexity of coroutines should not be too high

           Code Smell
        7. Cyclomatic Complexity of coroutines should not be too high

           Code Smell
        8. Coroutines should not have too many lines of code

           Code Smell
        9. "std::scoped_lock" should be used instead of "std::lock_guard"

           Code Smell
        10. Cognitive Complexity of functions should not be too high

           Code Smell
        11. "goto" statements should not be used to jump into blocks

           Code Smell
        12. Structures should not have too many fields

           Code Smell
        13. The ternary operator should not be used

           Code Smell
        14. Cyclomatic Complexity of functions should not be too high

           Code Smell
        15. "switch" statements should not have too many "case" clauses

           Code Smell
        16. Classes should not have too many methods

           Code Smell
        17. Functions/methods should not have too many lines

           Code Smell
        18. Control flow statements "if", "for", "while", "switch" and "try" should not be nested too deeply

           Code Smell
        19. "switch case" clauses should not have too many lines of code

           Code Smell
        20. Functions should not contain too many return statements

           Code Smell
        21. Magic numbers should not be used

           Code Smell
        22. Functions should not have too many parameters

           Code Smell
        23. Expressions should not be too complex

           Code Smell
        24. Files should not have too many lines of code

           Code Smell
        25. A function should have a single point of exit at the end of the function

           Code Smell

        A function should have a single point of exit at the end of the function

        consistency - conventional
        maintainability
        Code Smell
        • based-on-misra
        • brain-overload

        Why is this an issue?

        More Info

        This is required by IEC 61508, under good programming style.

        Noncompliant code example

        int function1()
        {
          return 3;
        }
        
        void function2()
        {
          function1();
        }
        
        int function3(char* ptr) /* Noncompliant; two explicit returns */
        {
          if (ptr == NULL) return -1;
        
          return 7;
        }
        
        void function4(char *ptr) /* Noncompliant; two returns, one explicit and one implicit */
        {
          if (1) return;
        
          printf("hello world!\n");
        }
        
          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 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