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
Go

Go static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your GO code

  • All rules 94
  • Vulnerability21
  • Bug13
  • Security Hotspot14
  • Code Smell46
 
Tags
    Impact
      Clean code attribute
        1. Busy waiting loops should use proper synchronization

           Bug
        2. HTTP response bodies should be closed to prevent resource leaks

           Bug
        3. Deprecated "InterfaceData" method should not be used

           Bug
        4. Custom error types must implement "Error()" method correctly

           Bug
        5. Database transactions should be properly handled with rollback mechanisms

           Bug
        6. Test functions should not call "t.Fatal" from separate goroutines

           Bug
        7. All branches in a conditional structure should not have exactly the same implementation

           Bug
        8. Non-existent operators like "=+" should not be used

           Bug
        9. Related "if/else if" statements should not have the same condition

           Bug
        10. Identical expressions should not be used on both sides of a binary operator

           Bug
        11. All code should be reachable

           Bug
        12. Variables should not be self-assigned

           Bug
        13. Useless "if(true) {...}" and "if(false){...}" blocks should be removed

           Bug

        Useless "if(true) {...}" and "if(false){...}" blocks should be removed

        Bug
        • cwe

        Why is this an issue?

        More Info

        if statements with conditions that are always false have the effect of making blocks of code non-functional. if statements with conditions that are always true are completely redundant, and make the code less readable.

        There are three possible causes for the presence of such code:

        • An if statement was changed during debugging and that debug code has been committed.
        • Some value was left unset.
        • Some logic is not doing what the programmer thought it did.

        In any of these cases, unconditional if statements should be removed.

        Noncompliant code example

        if true {
        	doSomething()
        }
        
        if false {
        	doSomething()
        }
        

        Compliant solution

        doSomething();
        ...
        
          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

        © 2025 SonarSource Sàrl. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use