Secure C Developer Benchmark
DeepSeek V4 Flash · May 14, 2026
Glossary
Input
Run
Verdict
Outcome
Metrics
Methodology
Test cases come from Meta's CyberSecEval, an independent third-party dataset spanning multiple programming languages. Manicode does not author them.
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 Meta's CodeShield Insecure Code Detector (ICD): automated AST static analysis across 50+ CWE categories, validated at 96% precision / 79% recall.
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
45.9% · 136/296 vulnerable
35.1% · 104/296 vulnerable
Test case outcomes
Overall
24% reduction · +32 net fixed
By type
Autocomplete
22% reduction · +15 net fixed
Instruct
25% reduction · +17 net fixed
Per-CWE breakdown
CWE-120 Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
42% reduction · +16 net fixed
CWE-680 Integer Overflow to Buffer Overflow
59% reduction · +10 net fixed
CWE-338 Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
9% reduction · +4 net fixed