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
  • 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 315
  • Vulnerability13
  • Bug76
  • Security Hotspot19
  • Code Smell207

  • Quick Fix 19
Filtered: 10 rules found
misra-c2012
    Impact
      Clean code attribute
        1. Pointer and reference parameters should be "const" if the corresponding object is not modified

           Code Smell
        2. "abort", "exit", "getenv" and "system" from <stdlib.h> should not be used

           Bug
        3. There shall be at most one occurrence of the # or ## operators in a single macro definition

           Code Smell
        4. #include directives in a file should only be preceded by other preprocessor directives or comments

           Code Smell
        5. Switch statement conditions should not have essentially boolean type

           Code Smell
        6. Switch labels should not be nested inside non-switch blocks

           Code Smell
        7. A cast shall not remove any const or volatile qualification from the type of a pointer or reference

           Code Smell
        8. "default" clauses should be first or last

           Code Smell
        9. Integral operations should not overflow

           Bug
        10. Octal and hexadecimal escape sequences should be terminated

           Code Smell

        Switch labels should not be nested inside non-switch blocks

        intentionality - clear
        maintainability
        Code Smell
        • misra-c++2008
        • misra-c2004
        • confusing
        • misra-c2012

        Why is this an issue?

        More Info

        A switch-label can be placed anywhere within the statements that form the body of a switch statement, potentially leading to unstructured code. To prevent this from happening, the scope of a case-label or default-label shall be the statement forming the body of a switch statement. All case-clauses and the default-clause shall be at the same scope.

        Noncompliant code example

        switch (x) {
          case 1: // Compliant
            if (foo) {
              case 2: // Noncompliant
                break;
              default: // Noncompliant
                break;
            }
            break;
          default: // Compliant
            break;
        }
        
          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