Code analysis (SAST & code quality)
How this is scored
What the tool finds in the company's own code: static application security testing with data-flow and taint analysis across functions and files, the languages and frameworks covered and at what depth, the rule sets (OWASP Top 10, CWE, custom rules), bugs and code smells, duplication, cyclomatic and cognitive complexity, maintainability and technical-debt measures, test coverage import, infrastructure-as-code checks, and how false positives are measured and kept down.
0 — Does not analyse source code; a dependency, secret or runtime scanner only, or a different kind of product.
3 — Pattern-based rules or linters for a handful of languages; data-flow analysis, the rule list, quality metrics and false-positive handling are basic or not described.
5 — SAST for the common languages (Java, JavaScript/TypeScript, Python, C#, Go, PHP) with the rule list published and mapped to OWASP and CWE, bugs and code smells, duplication and complexity metrics, coverage import, and custom rules or rule configuration documented.
8 — Cross-file taint analysis with the supported frameworks listed per language, a rule language customers can write in, infrastructure-as-code checks, maintainability or code-health scores over time, false-positive rates or benchmarks published, and each finding explained with its data flow and a fix.
10 — Analysis a large polyglot codebase relies on: deep interprocedural analysis across many languages with the depth stated per language, independent benchmark results, quality and security trends per team and hotspot, and every rule documented with examples and its precision.
The Skeptic
The taint engine is real and documented: security-injection rules track untrusted input from source to sink, findings display their flows, and you can configure your own sources, sanitizers, validators and sinks for homemade frameworks, with OWASP Top 10 (2025/2021/2017), CWE Top 25, ASVS and other standards coverage listed per language and IaC checks for Terraform, CloudFormation, ARM, Kubernetes and Ansible. What I want and do not get is independent proof of precision: the only published false-positive figure I can find is under five percent for secrets detection, while the SAST engine itself gets "high precision" language, and per-language depth is stated only for Advanced SAST (Java, C#) and reachability analysis (Java/Kotlin, Python, C#/VB.NET). 2 3 4 8 21 29