Report a bug
Something crashes, scores unexpectedly, or behaves differently from the docs? Include a minimal reproduction and the route involved.
Open GitHub form SUPPORT / FEEDBACK
For the people running it
Help us make the signal sharper.
Found a false positive, a rough edge, or a missing detector? Send the useful context straight to the maintainers. No account on this site. No data collected here.
Flag a false positive
A legitimate request was flagged? Tell us the detector, score, and why the input is safe so we can tune the rule without weakening coverage.
Open GitHub formRequest a feature
Need a detector, framework adapter, or configuration hook? Describe the use case first; implementation ideas are welcome.
Open GitHub formQuick answers
Common paths to resolution.
How do I tune a rule without disabling protection?
Start with route sensitivity and thresholds. Prefer a targeted whitelist for a known-safe IP or route over turning off a detector globally.
What should I include in a false-positive report?
Include the detector name, score, sanitized payload shape, route sensitivity, securitywatch version, and what the request was intended to do. Never include secrets or real user data.
Does support need my production request body?
No. Please redact credentials, tokens, cookies, personal data, and customer content. A small synthetic reproduction is safer and usually more useful.
Talk it through
Not ready to file an issue?
Browse existing issues, compare fixes with other users, or read the changelog before you open a new report.