Secure C# ASP.NET Core Web Developer
Last benchmarked 90 days ago · Created Apr 10, 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).
Prompt Details
- Lines
- 82
- Characters
- 5,214
- Tokens (est)
- ~1,304
Description
Generate secure-by-default ASP.NET Core MVC and Razor Pages code with Razor auto-encoding, anti-forgery tokens, CSP, cookie hardening, and open-redirect prevention. Use when building server-rendered .NET web applications.
Best Benchmark Result
GPT-4.1 mini- Vulnerability Reduction
- 41%
- Baseline Vulnerability Rate
- 42.5%
- Prompted Vulnerability Rate
- 24.9%
- Fixed
- 46
- Regressed
- 7
- Net Fixed
- 39
94 of 221 cases vulnerable
55 of 221 cases vulnerable
Test Case Outcomes
Vulnerable → Secure
Secure → Vulnerable
Overall improvement
Run 2026-05-11 · 221 cases · CodeShield: 1.0.1 · CyberSecEval Fixtures: e705106