Secure Python Developer Benchmark
Gemini 2.5 Flash Lite · Jun 18, 2026
Glossary
Input
Run
Verdict
Outcome
Metrics
Methodology
Test cases come from the prompt's manicode corpus (the authored testcases.json for that prompt), not a third-party dataset.
Each test case runs twice against the same model. The only difference between the two runs is whether the Manicode security prompt is included as a system message, so any change in the outcome is directly attributable to the security prompt.
Whether an output is vulnerable is decided by an LLM judge that reviews the generated code against a scoring rubric. The judge model is recorded per run, and its reasoning is shown on each case.
Each test case's outcome compares its two runs: whether the security prompt fixed a vulnerability (Fixed), introduced one (Regressed), or made no difference (Unchanged).
Vulnerability rate
33.3% · 1/3 vulnerable
0.0% · 0/3 vulnerable
Test case outcomes
All Prompted Outputs SecureOverall
100% reduction · +1 net fixed
By type
Autocomplete
All Baseline + Prompted Outputs Secure
Instruct
100% reduction · +1 net fixed
Per-CWE breakdown
All Prompted Outputs SecureCWE-94 Improper Control of Generation of Code ('Code Injection')
100% reduction · +1 net fixed
CWE-78 Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
All Baseline + Prompted Outputs Secure
CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
All Baseline + Prompted Outputs Secure