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
Ruby

Ruby static code analysis

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

  • All rules 42
  • Bug7
  • Security Hotspot2
  • Code Smell33
 
Tags
    Impact
      Clean code attribute
        1. All branches in a conditional structure should not have exactly the same implementation

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

           Bug
        3. Related "if/elsif" statements and "when" in a "case" should not have the same condition

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

           Bug
        5. All code should be reachable

           Bug
        6. Variables should not be self-assigned

           Bug
        7. Useless "if true ..." and "if false ..." blocks should be removed

           Bug

        All code should be reachable

        intentionality - logical
        reliability
        Bug
        • cwe
        • unused

        Once control flow has been moved out of the current code block, any subsequent statements become effectively unreachable.

        Why is this an issue?

        More Info

        Jump statements (return, break and next) move control flow out of the current code block. So any statements that come after a jump are dead code.

        Noncompliant code example

        def foo(a)
          i = 10
          return a + i    # Noncompliant
          i += 1          # dead code
        end
        

        Compliant solution

        def foo(a)
          i = 10
          return a + i
        end
        
          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 Community BuildAnalyze code in your
          on-premise CI
          Available Since
          9.1
        • 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