Security auditing for code, configs, and infrastructure. Use when the user wants to audit or improve security: scan for vulnerabilities (SQL injection, XSS, command injection, path traversal), detect hardcoded secrets and credentials, review auth and authorization, check dependencies for known CVEs, audit config files for insecure defaults, or generate security reports. Trigger on \"security audit\", \"vulnerability scan\", \"code review for security\", \"find secrets\", \"check for vulnerabilit
Install
KitScout test notes
Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.
Similar tools
ponytail-audit190,107 ★ Quality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most imp
ponytail-debt190,107 ★ Harvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot
security-and-hardening117,009 ★ Hardens code against vulnerabilities. Use when auditing an input handler for vulnerabilities, when handling us
deal-with-security-advisory113,555 ★ Handle confidential GitHub Security Advisory response for Paperclip. Use when coordinating advisory triage, pr
html-ppt-knowledge-arch-blueprint107,474 ★ OpenDesign's incident retro: the daemon-restart data bug, the root cause, the fix, and the systemic follow-ups