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
The code analysis engine builds an event graph of the codebase and runs rules against it, follows taint from application code into template engines such as Jinja2 and Thymeleaf including escaping behaviour, and documents framework support per language at Comprehensive and Partial levels with stated limitations such as possible false negatives in taint analysis. Findings in the IDE carry the data flow and remediation guidance, and infrastructure-as-code results sit in the same dashboard, with documentation covering custom rules for infrastructure-as-code. We found no public information on a customer-writable rule language for application code, on quality metrics such as complexity and duplication, or on published false-positive rates or independent benchmarks; accuracy appears only as vendor claims such as 80%-accurate fixes and 25M+ modelled data flow cases. 16 2 21 4 17