How to fix: TODO/FIXME Security Note in Response
A TODO or FIXME comment referencing security, authentication, authorization, or validation was found in the HTTP response. This indicates unfinished security logic shipped to production.
Why it matters
Shipped TODO comments around security functionality indicate the protection is intentionally incomplete. Attackers scanning for these patterns can identify exactly where to probe for bypasses.
AI-assisted development frequently generates skeleton code with TODO stubs for security checks: 'TODO: add authentication', 'FIXME: validate input here', 'TODO: check permissions'. When this reaches production, the security check is absent by design.
How to fix it
- 1Grep the codebase for TODO/FIXME comments before every release.
- 2Enforce a lint rule (eslint-plugin-no-unsanitized, custom rules) that flags TODO comments in security-critical paths.
- 3Complete all security TODOs before shipping; never disable authentication 'temporarily'.
- 4Add a CI check that fails the build if security-related TODO comments exist in diff.
Code examples
Pattern to catch in CI
# Grep for security TODOs in changed files
git diff origin/main -- '*.ts' '*.js' | grep -i 'TODO.*\(auth\|security\|validate\|permission\|csrf\)'References
Detected automatically by VulnRadar. The check id is vibe-todo-security-comment, stable across every scan so you can filter or diff on it.
More ai code checks
- LowGeneric Error Messages Leak No Context
- Higheval() Usage in Page Scripts
- HighSSL Certificate Verification Disabled
- HighMath.random() Used for Security Tokens
- CriticalHardcoded Credential in Authentication Logic
- CriticalJWT 'none' Algorithm Accepted
- CriticalSQL String Concatenation Pattern Detected
- MediumStack Trace Exposed in Response
Questions
- How severe is TODO/FIXME Security Note in Response?
- VulnRadar rates this medium severity in the ai code category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id vibe-todo-security-comment, which stays the same between runs so you can filter, diff, or gate CI on it.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.