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
Flex

Flex static code analysis

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

  • All rules 76
  • Vulnerability5
  • Bug9
  • Security Hotspot1
  • Code Smell61
 
Tags
    Impact
      Clean code attribute
        1. The "trace" function should not be used

           Vulnerability
        2. Security.allowDomain(...) should only be used in a tightly focused manner

           Vulnerability
        3. The flash.system.Security.exactSettings property should never be set to false

           Vulnerability
        4. "LocalConnection" should be configured to narrowly specify the domains with which local connections to other Flex application are allowed

           Vulnerability
        5. "Alert.show(...)" should not be used

           Vulnerability

        The "trace" function should not be used

        Vulnerability

          This rule is deprecated; use S4507 instead.

          Why is this an issue?

          More Info

          The trace() function outputs debug statements, which can be read by anyone with a debug version of the Flash player. Because sensitive information could easily be exposed in this manner, trace() should never appear in production code.

          Noncompliant code example

              var val:Number = doCalculation();
              trace("Calculation result: " + val);  // Noncompliant
          

          Compliant solution

              var val:Number = doCalculation();
          
            Available In:
          • 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