Loophole is maintained in the open on GitHub — issues are the front door for everything: bugs, false positives, new-rule ideas and questions.
Open an issue in the repository. A minimal code snippet that reproduces the problem (or that a new rule should catch) is the single most helpful thing you can include — it usually becomes a test fixture.
Open a GitHub IssueFound a vulnerability in Loophole itself? Please follow the project's security policy instead of opening a public issue, so it can be fixed before details are shared.
For general questions, collaborations or just to follow the work, reach the maintainer, Muhamad Raza Haider, on GitHub:
@rootsiemen on GitHubWe deliberately don't publish an email address here — GitHub keeps everything in one public, searchable place, and issue threads help the next person with the same question. Privacy questions are covered by the Privacy Policy.