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
Text

Text static code analysis

Unique rules to find Security Hotspots and Offensive Text in any files

  • All rules 3
  • Security Hotspot2
  • Code Smell1
Filtered: 1 rule found
respectful
    Impact
      Clean code attribute
        1. Don't use offensive language

           Code Smell

        Don't use offensive language

        responsibility - respectful
        maintainability
        Code Smell
        • respectful

        Clean code should not make use of offensive language but instead use neutral and inclusive terminology.

        Why is this an issue?

        How can I fix it?

        More Info

        Code is meant to be understandable and clear to the reader. Discriminatory and offensive language is often used for expressiveness. Such language has made its way into technical jargon and code despite being derived from specific cultural contexts that carry discriminatory connotations. These terms are often idiomatic expressions that can be misleading and using such terms can perpetuate negative biases and hinder effective communication.

        For instance, the term sanity check is derived from psychiatric sanity, which can have a negative connotation with respect to a person’s mental health. Code itself cannot be in a state of sanity or, conversely, insanity. In the context of code, more precise and descriptive alternatives, such as validation check or verification check, exist and provide a clearer meaning. By choosing unambiguous and neutral terminology, we promote inclusivity and reduce the ambiguity of code.

        Companies with a mandate for inclusivity need to build products for everyone with the following considerations:

        • Brand reputation:
          • The adoption of respectful language in code aligns with evolving industry standards to position a brand as a leader in innovation and professionalism and avoid reputational damage and backlash.
          • Example: Facebook’s ad-serving algorithm discriminates by gender and race | MIT Technology Review
        • Employee Relations:
          • Respectful and inclusive language in code reflects a respectful and inclusive workplace culture.
          • Clear language in code fosters better understanding and communication among team members.
        • Legal/Regulatory Compliance:
          • Compliance with legal requirements and industry regulations.
          • Neutral and inclusive terminology minimizes the risk of litigation.
          • Example: Some changes to the public sector digital accessibility regulations
          Available In:
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Enterprise
          Edition
          Available Since
          sqs-10.8

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use