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 Platform Engineer
Taint analysis is real and documented: SQL injection tracked from source to sink with up to twenty flows shown, deeper taint analysis for Java and C#, and custom sources, sanitizers, validators and sinks configurable for our in-house frameworks, alongside custom rule development, IaC scanning for Terraform, Kubernetes and Ansible, and mappings to OWASP Top 10, CWE Top 25, PCI DSS and the EU Cyber Resilience Act. Quality measures include bugs, code smells, duplication, coverage and technical debt, and findings come with fix suggestions. Precision is only quantified for secrets detection (under 5% false positives), not for the SAST engine itself. 2 3 4 5 21