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
  • GroovyGroovy
  • 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
Groovy

Groovy static code analysis

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

  • All rules 21
  • Bug5
  • Code Smell16
 
Tags
    Impact
      Clean code attribute
        1. GString expressions should not be used as map keys

           Bug
        2. "@TimedInterrupt" should not be used on static methods

           Bug
        3. Null checks should use correct logical operators

           Bug
        4. Classes with a "clone()" method should implement "Cloneable"

           Bug
        5. "wait()" calls should be inside "while" loops

           Bug

        GString expressions should not be used as map keys

        intentionality - logical
        reliability
        maintainability
        Bug

          This is an issue when GString expressions (strings containing ${} interpolation or $variable syntax) are used as keys in map literals or when calling map methods like put().

          Why is this an issue?

          What is the potential impact?

          How can I fix it?

          More Info

          GString objects and String objects have different hash codes, even when they represent identical text. This causes maps to fail matching keys when mixing GStrings and Strings.

          When a GString is used as a map key, lookups with an equivalent String will fail. For example, storing with "${name}" (where name is "John") and retrieving with "John" returns null.

          This violates expectations and leads to bugs, especially when keys are created dynamically in one part of the code and used as literals elsewhere.

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

          © 2026 SonarSource Sàrl. All rights reserved.

          Privacy Policy | Cookie Policy | Terms of Use