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: 3 rules found
full-project
    Impact
      Clean code attribute
        1. Functions that are not used in a project should be removed

           Code Smell
        2. Server hostnames should be verified during SSL/TLS connections

           Vulnerability
        3. Server certificates should be verified during SSL/TLS connections

           Vulnerability

        Functions that are not used in a project should be removed

        intentionality - clear
        maintainability
        Code Smell
        • full-project
        • unused

        Why is this an issue?

        Unless you are in a library codebase context, functions that are declared in your program but never executed are dead code that should be removed. Cleaning out dead code decreases the size of the maintained codebase, making it easier to understand the program and preventing bugs from being introduced.

        Note: S1144 is a subset of this rule; hence, it should be deactivated when this rule is activated.

        Noncompliant code example

        void unusedStaticFunction() { // Noncompliant
        }
        
        void unusedGlobalFunction() { // Noncompliant: it is not called in the entire program
        }
        
        void undefinedGlobalFunction(); // Noncompliant
        
        class A {
        public:
          A(int i) : i(i){} // Compliant it is called in "main"
          void startUsed() { // Compliant, the member function "startUsed" is called in "main"
          }
          void startUnused() { // Noncompliant, the member function "startUnused" is not called in the program
          }
        private:
          A(): i(0) { // Compliant, private and deleted constructor are an exception
          }
          int i;
        };
        
        int main() // Compliant, "main" is an exception.
        {
          A a{2};
          a.startUsed();
        }
        
          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