Source
Documentation (taint analysis) — Qodana
Checked for Qodana on 6 Nov 2026
- Page
- https://www.jetbrains.com/help/qodana/taint-analysis.html
- Checked
- 6 Nov 2026, 05:14 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:bcf62a3456fcef8f897a965a486bd0d03f316166a01713412c2db7d13cef4d33
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Taint analysis purpose Report an error
“Taint analysis lets you trace the flow of potentially harmful or tainted data through a program. It identifies paths where untrusted input or sources might reach sensitive operations or sinks without proper validation or sanitization, which helps prevent security vulnerabilities like SQL injections, cross-site scripting (XSS), command injections, and path traversal.”
-
Taint analysis license requirement Report an error
“Taint analysis is supported by IntelliJ IDEA Ultimate, as well as by the Qodana for PHP, Qodana for JVM, and the Qodana for .NET linters under the Ultimate Plus license.”
-
Taint analysis owasp top10 2021 categories Report an error
“This feature provides built-in taint rules for the most common categories of OWASP Top 10:2021 vulnerabilities (A01, A03, A07, A08, A10).”
-
Taint analysis custom rules Report an error
“In addition to the built-in rules, you can configure custom taint rules for your own application or library code, designating specific functions or methods as sources or sinks.”
-
Taint analysis local execution Report an error
“The taint analysis feature runs locally and does not require any external dependencies or services.”
-
Taint analysis dotnet opengrep rules Report an error
“Starting from version 2026.2, the Qodana for .NET linter supports rules compatible with Opengrep for configuring taint analysis. It already includes a set of built-in C#, JavaScript, and TypeScript rules that you can use as Qodana inspections, so you don’t have to download or configure them manually.”
-
Taint analysis idea plugin Report an error
“Before you run taint analysis in your IDE, install the Security Analysis by Qodana plugin.”
-
Taint analysis linter profile requirement Report an error
“Taint analysis is available for the Qodana for PHP and Qodana for JVM linters once you invoke the qodana.recommended inspection profile”
-
Taint analysis dotnet enabled by default Report an error
“For the Qodana for .NET linter, taint analysis is enabled by default.”
-
Taint analysis in editor time limit Report an error
“The Analysis time limit for in-editor analysis (ms) field configures the amount of time that can be allocated for a specific file. The default value is 5000 ms.”
-
Taint analysis depth levels Report an error
“The Analysis depth (from a current file) field configures analysis depth using the Current file → File 1 (Low) → File 2 (Medium) → File 3 (High) reference pattern.”
-
Taint analysis default projection Report an error
“If there is no specific configuration available for a library function call, a projection will be applied by default. This means the taint status of the function arguments will be passed to the return value”
-
Taint analysis custom source sink example Report an error
“java.net.URI.getQuery can be configured as a source of tainted data to represent a point where potentially untrusted input enters the system. java.io.OutputStream.write can be configured as a sink where potentially tainted data may be written to an output stream, such as a file or network socket.”
-
Taint analysis config file Report an error
“This will create the inspections/config.inspection.kts file for a source, sink, and sanitizer configuration. To ensure consistency of analysis reports save this file in the root directory of your project.”
-
Taint analysis php inspection Report an error
“In the qodana.yaml file, include the PhpVulnerablePathsInspection inspection into the analysis scope”
-
Taint analysis max traces default Report an error
“By default, taint analysis is configured for monitoring one hundred (100) traces at a time. You can override this using the dfa.analysis.rml.max.traces.count=<number> property”
-
Taint analysis bundled rules disable property Report an error
“You can disable the bundled rules by configuring the intellij.opengrep.bundled.rules.enabled property”
-
Taint analysis custom rules directory Report an error
“In addition to the bundled rules, you can apply your own rules by saving rule files to the .qodana/opengrep directory of your project root.”
-
Taint analysis ci platforms Report an error
“Docker image Qodana CLI GitHub Actions Jenkins GitLab CI/CD TeamCity”
-
Taint analysis owasp 2017 coverage Report an error
“OWASP Top 2017 Coverage Matrix”
-
Taint analysis owasp 2021 coverage Report an error
“OWASP Top 2021 Coverage Matrix”
Scores citing this record
- The Application Security Engineer Code analysis (SAST & code quality)
- The Application Security Engineer Source-code handling, security & compliance
- The Engineering Manager Code analysis (SAST & code quality)
- The Engineering Manager Source-code handling, security & compliance
- The Lead Developer Code analysis (SAST & code quality)
- The Lead Developer Source-code handling, security & compliance
- The Platform Engineer Code analysis (SAST & code quality)
- The Product Security Officer Code analysis (SAST & code quality)
- The Product Security Officer Pricing transparency
- The Skeptic Code analysis (SAST & code quality)