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 493
  • Vulnerability46
  • Bug88
  • Security Hotspot24
  • Code Smell335

  • Quick Fix 61
Filtered: 17 rules found
symbolic-execution
    Impact
      Clean code attribute
        1. Locks should be released within the same method

           Bug
        2. A write lock should not be released when a read lock has been acquired and vice versa

           Bug
        3. First/Single should be used instead of FirstOrDefault/SingleOrDefault on collections that are known to be non-empty

           Code Smell
        4. JWT secret keys should not be disclosed

           Vulnerability
        5. Types allowed to be deserialized should be restricted

           Vulnerability
        6. Secure random number generators should not output predictable values

           Vulnerability
        7. Empty collections should not be accessed or iterated

           Bug
        8. Objects should not be disposed more than once

           Code Smell
        9. Calculations should not overflow

           Bug
        10. Arguments of public methods should be validated against null

           Code Smell
        11. Empty nullable value should not be accessed

           Bug
        12. Cipher Block Chaining IVs should be unpredictable

           Vulnerability
        13. Boolean expressions should not be gratuitous

           Code Smell
        14. Conditionally executed code should be reachable

           Bug
        15. Null pointers should not be dereferenced

           Bug
        16. Locks should be released on all paths

           Bug
        17. Password hashing functions should use an unpredictable salt

           Vulnerability

        Boolean expressions should not be gratuitous

        intentionality - logical
        maintainability
        Code Smell
        • cwe
        • suspicious
        • redundant
        • symbolic-execution

        Gratuitous boolean expressions are conditions that do not change the evaluation of a program. This issue can indicate logical errors and affect the correctness of an application, as well as its maintainability.

        Why is this an issue?

        How can I fix it?

        More Info

        Control flow constructs like if-statements allow the programmer to direct the flow of a program depending on a boolean expression. However, if the condition is always true or always false, only one of the branches will ever be executed. In that case, the control flow construct and the condition no longer serve a purpose; they become gratuitous.

        What is the potential impact?

        The presence of gratuitous conditions can indicate a logical error. For example, the programmer intended to have the program branch into different paths but made a mistake when formulating the branching condition. In this case, this issue might result in a bug and thus affect the reliability of the application. For instance, it might lead to the computation of incorrect results.

        Additionally, gratuitous conditions and control flow constructs introduce unnecessary complexity. The source code becomes harder to understand, and thus, the application becomes more difficult to maintain.

        This rule looks for operands of a boolean expression never changing the result of the expression. It also applies to the null coalescing operator when one of the operands always evaluates to null.

        string d = null;
        var v1 = d ?? "value";      // Noncompliant
        

        Exceptions

        This rule will not raise an issue in either of these cases:

        • When the condition is a single const bool
          const bool debug = false;
          //...
          if (debug)                  // Compliant
          {
            // Print something
          }
          
        • When the condition is the literal true or false.

        In these cases, it is obvious the code is as intended.

          Available In:
        • 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