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

        Cognitive Complexity of coroutines should not be too high

        adaptability - focused
        maintainability
        Code Smell
        • since-c++20
        • brain-overload

        Why is this an issue?

        More Info

        "Cognitive complexity" is a measure of how hard the control flow of a function is to understand. Code with high cognitive complexity is hard to read, understand, test, and modify.

        This rule raises on coroutines with high cognitive complexity.

        As a rule of thumb, high cognitive complexity is a sign that the code should be refactored into smaller, easier-to-manage pieces.

        Which syntax in code does impact cognitive complexity score?

        Here are the core concepts:

        • Cognitive complexity is incremented each time the code breaks the normal linear reading flow.
          This concerns, for example, loop structures, conditionals, catches, switches, jumps to labels, and conditions mixing multiple operators.
        • Each nesting level increases complexity.
          During code reading, the deeper you go through nested layers, the harder it becomes to keep the context in mind.
        • Method calls are free
          A well-picked method name is a summary of multiple lines of code. A reader can first explore a high-level view of what the code is performing then go deeper and deeper by looking at called functions content.
          Note: This does not apply to recursive calls, those will increment cognitive score.

        The method of computation is fully detailed in the pdf linked in the resources.

          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.3

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use