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 Application Security Engineer
Cross-file taint tracking is documented for twelve languages including JavaScript, TypeScript, Java,.NET/C#, Python and Go, with the scope stated per language (seven more such as Swift and Kotlin are tracked within files only), custom SAST rules are creatable via UI and API, and infrastructure-as-code runs on Terraform, CloudFormation, Docker and Pulumi. False-positive reduction is claimed at 90 percent with a published 32-second scan time, but we found no public information on independent benchmarks, per-rule precision or per-finding data-flow walkthroughs. The plain statement that SAST will not catch logic or authorization flaws matching no known pattern, with Deep Review and AI Code Analysis offered as complements, is the kind of honest scoping I need when sizing a remediation backlog. 17 2 8 6