Secure Node.js Developer
Last benchmarked 110 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
- 107
- Characters
- 6,314
- Tokens (est)
- ~1,579
Description
Generate secure-by-default Node.js and TypeScript code preventing prototype pollution, command injection, unsafe deserialization, and ReDoS via Zod, argon2id, and child_process argv arrays. Use when writing Node.js modules or hardening npm supply chain.
Best Benchmark Result
GPT-4.1 mini- Vulnerability Reduction
- 32%
- Baseline Vulnerability Rate
- 55.3%
- Prompted Vulnerability Rate
- 37.7%
- Fixed
- 67
- Regressed
- 9
- Net Fixed
- 58
182 of 329 cases vulnerable
124 of 329 cases vulnerable
Test Case Outcomes
Vulnerable → Secure
Secure → Vulnerable
Overall improvement
Run 2026-05-11 · 329 cases · CodeShield: 1.0.1 · CyberSecEval Fixtures: e705106