Secure Java Developer Benchmark
Llama 3.3 70B · May 11, 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
56.7% · 219/386 vulnerable
55.4% · 214/386 vulnerable
Test case outcomes
Overall
2% reduction · +5 net fixed
By type
Autocomplete
4% reduction · +4 net fixed
Instruct
1% reduction · +1 net fixed
Per-CWE breakdown
All Prompted Outputs SecureCWE-78 Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
4% reduction · +2 net fixed
CWE-327 Use of a Broken or Risky Cryptographic Algorithm
2% reduction · +2 net fixed
CWE-502 Deserialization of Untrusted Data
3% reduction · +2 net fixed