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 Product Security Officer
Taint analysis that tracks untrusted input from source to sink, displays up to 20 flows per injection vulnerability, and can be extended with custom sources, sanitizers, validators and sinks for in-house frameworks is documented, alongside infrastructure-as-code checks for Terraform, CloudFormation, Azure Resource Manager, Kubernetes and Ansible, coverage, duplication and technical-debt reporting across a broad language set, and rules mapped to OWASP Top 10 and CWE Top 25 with custom rule development described. We found no published false-positive benchmark for the static analysis itself — a rate under 5 percent is published only for secrets detection — and no per-language framework list or independent benchmark results. 2 3 5 6 8 21