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

        Deprecated "InterfaceData" method should not be used

        intentionality - logical
        reliability
        maintainability
        Bug
        • deprecated
        • go

        This rule raises an issue when the deprecated reflect.Value.InterfaceData() method is called.

        Why is this an issue?

        How can I fix it?

        More Info

        The reflect.Value.InterfaceData() method has been deprecated since Go 1.4 and should not be used in modern Go code.

        In earlier versions of Go, this method returned the interface’s value as a uintptr pair. However, as of Go 1.4, changes to the implementation of interface values mean that InterfaceData() has no defined use. The memory representation of interface values is no longer compatible with the data returned by this method.

        Using deprecated methods can lead to several problems:

        • Unpredictable behavior: The method may not work as expected due to internal implementation changes
        • Future compatibility issues: Deprecated methods may be removed in future Go versions
        • Maintenance burden: Code using deprecated APIs becomes harder to maintain and update

        The Go documentation explicitly states that the memory representation of interface values is not compatible with InterfaceData, making any use of this method unreliable and potentially dangerous.

        What is the potential impact?

        Using the deprecated InterfaceData() method can lead to unpredictable behavior and runtime issues. Since the method has no defined use and the underlying memory representation has changed, code relying on it may produce incorrect results or fail unexpectedly. Additionally, future Go versions may remove this method entirely, breaking code that depends on it.

          Available In:
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories

        © 2025 SonarSource Sàrl. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use