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
Java

Java static code analysis

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

  • All rules 733
  • Vulnerability60
  • Bug175
  • Security Hotspot40
  • Code Smell458

  • Quick Fix 65
Filtered: 20 rules found
android
    Impact
      Clean code attribute
        1. Processing persistent unique identifiers is security-sensitive

           Security Hotspot
        2. Exposing native code through JavaScript interfaces is security-sensitive

           Security Hotspot
        3. Bluetooth should be configured to use low power

           Code Smell
        4. Motion Sensor should not use gyroscope

           Code Smell
        5. Use Fused Location to optimize battery power

           Code Smell
        6. High frame rates should not be used

           Code Smell
        7. Exact alarms should not be abused

           Code Smell
        8. Proper Sensor Resource Management

           Code Smell
        9. Components should not be vulnerable to intent redirection

           Vulnerability
        10. Enabling file access for WebViews is security-sensitive

           Security Hotspot
        11. Enabling JavaScript support for WebViews is security-sensitive

           Security Hotspot
        12. Mobile database encryption keys should not be disclosed

           Vulnerability
        13. Using biometric authentication without a cryptographic solution is security-sensitive

           Security Hotspot
        14. Authorizing non-authenticated users to use keys in the Android KeyStore is security-sensitive

           Security Hotspot
        15. Using clear-text protocols is security-sensitive

           Security Hotspot
        16. Accessing Android external storage is security-sensitive

           Security Hotspot
        17. Receiving intents is security-sensitive

           Security Hotspot
        18. Broadcasting intents is security-sensitive

           Security Hotspot
        19. Database queries should not be vulnerable to injection attacks

           Vulnerability
        20. URIs should not be hardcoded

           Code Smell

        Motion Sensor should not use gyroscope

        consistency - conventional
        maintainability
        Code Smell
        • android
        • sustainability

        The android.hardware.SensorManager#getDefaultSensor offers two types of Motion Sensors:

        • TYPE_ROTATION_VECTOR: a combination of the gyroscope, accelerometer, and magnetometer.
        • TYPE_GEOMAGNETIC_ROTATION_VECTOR: a combination of the accelerometer and magnetometer.

        Why is this an issue?

        How can I fix it?

        More Info

        The battery life is a major concern for mobile devices and choosing the right Sensor is very important to reduce the power usage and extend the battery life.

        It is recommended, for reducing the power usage, to use TYPE_GEOMAGNETIC_ROTATION_VECTOR for background tasks, long-running tasks and other tasks not requiring accurate motion detection.

        The rule reports an issue when android.hardware.SensorManager#getDefaultSensor uses TYPE_ROTATION_VECTOR instead of TYPE_GEOMAGNETIC_ROTATION_VECTOR.

          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
          10.5
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Developer Edition
          Available Since
          10.5

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use