Feedback / and support
Found a problem, or want a tool built?
Everything here opens a pre-filled issue on GitHub. That is deliberate rather than a shortcut — issues are public, so you can see whether anyone else hit the same thing, follow the fix, and hold me to it. There is no contact form because there is no server behind this site, and adding one would break the guarantee that nothing you paste into these tools leaves your browser.
Report a bug
BugA tool errors, renders wrong, or behaves differently from what it documents. The template asks for the browser and the triggering input, which is usually enough to reproduce it first try.
Flag an incorrect finding
AccuracyThe highest-priority category. A tool that reports something false is worse than no tool, because the output goes into client reports. If a severity, impact claim or remediation is wrong, this is the one to use.
Request a tool
RequestDescribe the manual task you want to stop doing. The most useful requests name the tools you use today and what they get wrong — that is what makes a replacement worth building.
Suggest an improvement
FeatureA missing check, an export format, a keyboard shortcut, an extra platform in the remediation snippets.
Ask a question
QuestionHow to use something, why a tool reached a particular verdict, or how to read a result before putting it in a report.
Browse open issues
AllCheck whether something is already reported or already fixed before writing it up.
Join the cybersecurity community
A group for people working in or breaking into security — sharing writeups, answering questions, and passing along the things that are hard to find on your own. Open to anyone: students, freshers, and people already doing the work.
Sign up with the form below. It is a Google Form, so it opens
on docs.google.com and is handled there rather than on this site.