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: 9 rules found
obsolete
    Impact
      Clean code attribute
        1. Digraphs should not be used

           Code Smell
        2. Trigraphs should not be used

           Code Smell
        3. GNU extensions should not be used

           Code Smell
        4. Increment should not be used to set boolean variables to 'true'

           Code Smell
        5. Obsolete POSIX functions should not be used

           Code Smell
        6. Code annotated as deprecated should not be used

           Code Smell
        7. Deprecated K&R syntax should not be used for function definition

           Code Smell
        8. Deprecated code should be removed

           Code Smell
        9. Deprecated attributes should include explanations

           Code Smell

        Deprecated attributes should include explanations

        intentionality - clear
        maintainability
        Code Smell
        • obsolete
        • bad-practice

        Why is this an issue?

        The deprecated attribute can be applied with or without explanations, but marking something deprecated without including advice as to why it’s deprecated or on what to use instead will lead maintainers to waste time trying to figure those things out - every single time the warning is encountered.

        Noncompliant code example

        [[deprecated]] // Noncompliant
        void foo1();
        
        __attribute__((deprecated)) // Noncompliant
        void foo2();
        
        __declspec(deprecated) // Noncompliant
        void foo3();
        

        Compliant solution

        [[deprecated("use 'bar' instead")]]
        void foo1();
        
        __attribute__((deprecated("use 'bar' instead")))
        void foo2();
        
        __declspec(deprecated("use 'bar' instead"))
        void foo3();
        
          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