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
This is the question I always ask first — which languages get real data-flow — and the answer is documented: tainted input is tracked across multiple files for twelve languages including Java, TypeScript, Python, C# and Go, and within single files only for seven more (Swift, Kotlin, Dart, Elixir and friends), with custom SAST rules, infrastructure-as-code checks via Checkov, and fixes carrying confidence scores. The captured pages give different figures for false-positive reduction — 90% on two pages, 99% on the homepage — and I found no independent benchmark or per-rule precision data behind either number. Findings adjust to context (sensitive repositories upgraded, test files downgraded), and the vendor openly states SAST will not catch logic or authorization bugs that do not match known patterns. 17 2 6 1 8 5