Correctness
Does the proposed fix resolve the underlying issue without breaking functionality?
Measures whether AI models can recommend, generate, and validate fixes for vulnerabilities found by static analysis tools across major programming languages and SAST engines.
Each model response is judged on these dimensions by an LLM-as-Judge calibrated against expert annotations.
Does the proposed fix resolve the underlying issue without breaking functionality?
Does the fix avoid introducing new CVEs, regressions, or side-channel risks?
Does the model reason about the calling context, framework idioms, and data flow?
Is the fix directly applicable as a PR or patch without manual rewriting?
Does the model explain the root cause, blast radius, and trade-offs clearly?
An illustrative case to show how the model is presented with a problem and how its response is scored.
SQL injection in user.controller.ts line 42 — raw concatenation in WHERE clause.
Given the file, the finding, and surrounding call sites, generate a fix that resolves the SQLi while preserving the API contract.
Replace string concatenation with a parameterized prepared statement using the existing ORM. Add input validation. Justify the change in the PR description.
LLM-as-Judge rubric weighs Correctness (40%), Safety (25%), Context-Awareness (15%), Executability (15%), Explanation (5%).
All Remediation Labs benchmarks evolve through three versions, increasing in difficulty and realism.
Models are given the raw security finding and asked to recommend a remediation. No environment context provided.
Models receive the finding plus relevant system, code, and policy context. Evaluated on contextual reasoning quality.
Models must produce a remediation that can be safely executed end-to-end — code patches, IaC changes, runbook steps — with verification.
Get model leaderboards, scoring methodology, dataset details, and roadmap access — or discuss generating proprietary remediation datasets for your environment.
Or email us directly at info@remediationlabs.com