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

        Exact alarms should not be abused

        intentionality - efficient
        maintainability
        Code Smell
        • java
        • android
        • sustainability

        The AlarmManager class provides access to the system alarm services. It allows you to schedule your application to run at some point in the future, even when it’s not active.

        From API 19 onwards, the alarm delivery is inexact in order to save battery life. The Android OS now batches together alarms from all apps that occur at reasonably similar times so the system wakes the device once instead of several times to handle each alarm.

        It is possible to use exact alarms with setExact, setExactAndAllowWhileIdle, setWindow and setAlarmClock. Exact alarms should be used only when strict delivery guarantees are required, for example for an alarm clock application or for calendar notifications.

        The rule raises an issue when an exact alarm is set, or when a window is set to less than 10 minutes.

        Why is this an issue?

        How can I fix it?

        More Info

        The use of exact alarms triggers the device to wake up at precise times that can lead several wake-ups in a short period of time. The wake-up mechanism is a significant battery drain because it requires powering up the main processor and pulling it out of a low-power state.

        It’s highly recommended to create an inexact alarm whenever possible.

        It is also recommended for normal timing operations, such as ticks and timeouts, using the Handler, and for long-running operations, such as network downloads, using WorkManager or JobScheduler.

        What is the potential impact?

        • Usability: the device may run out of battery faster than expected.
        • Sustainability: the extra battery usage has a negative impact on the environment.
          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