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
Rust

Rust static code analysis

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

  • All rules 85
  • Bug60
  • Code Smell25

  • Quick Fix 4
Filtered: 2 rules found
bad-practice
    Impact
      Clean code attribute
        1. Loops with at most one iteration should be refactored

           Bug
        2. Standard outputs should not be used directly to log anything

           Code Smell

        Standard outputs should not be used directly to log anything

        adaptability - modular
        maintainability
        Code Smell
        • bad-practice
        • clippy

        Why is this an issue?

        More Info

        In software development, logs serve as a record of events within an application, providing crucial insights for debugging. When logging, it is essential to ensure that the logs are:

        • easily accessible
        • uniformly formatted for readability
        • properly recorded
        • securely logged when dealing with sensitive data

        Those requirements are not met if a program directly writes to the standard outputs (e.g., print!, println!). That is why defining and using a dedicated logger is highly recommended.

        Code examples

        Noncompliant code example

        fn do_something() {
            println!("my message");  // Noncompliant, output directly to stdout without a logger
        }
        

        Compliant solution

        use log::{info, LevelFilter};
        use simple_logger::SimpleLogger;
        
        fn do_something() {
            SimpleLogger::new().with_level(LevelFilter::Info).init().unwrap();
            // ...
            info!("my message");  // Compliant, output via logger
            // ...
        }
        
          Available In:
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use