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 Lead Developer
Mend SAST publishes a CWE rule table mapped to OWASP Top 10, CAPEC and PCI DSS, with SQL injection, command injection, path traversal and hard-coded credentials covered for the PHP and TypeScript stacks my team builds in, plus an IaC module in the GitHub Enterprise app. Findings are consolidated by taint sink, carry risk factors for confidence and data-flow characteristics, default to high confidence to cut noise, and an AI triage explains the sanitizer, control-flow coverage and exploitation path — genuinely aimed at false positives. A custom rule language, published false-positive benchmarks, per-language framework depth and code-quality metrics like duplication or complexity are not described on the captured pages. 3 4 7 8 10