Code of Conduct complaint
This form handles community behaviour only: harassment, personal attacks, discrimination, and sustained disruptive interaction. It is a completely separate queue from security reports — GitHub Security Advisories feed into CVE workflows, so routing conduct complaints there is semantically wrong and slows down real vulnerabilities.
Technical vulnerabilities belong on the security page; ordinary bugs and feature requests belong in GitHub Issues.
Anonymous submissions are supported. Content is stored server-side and readable only through the private admin route — never published, never exposed to the browser.
Anonymous submissions are supported. Content is stored server-side and readable only through the private admin route — never published, never exposed to the browser.
How it is handled
| Acknowledgement | Usually within 72 hours (a target, not a hard SLA). |
|---|---|
| Confidentiality | The reporter's identity is not disclosed to the respondent by default; anonymous reports require no identity at all. |
| Ladder | Contributor Covenant 2.0 with the Mozilla enforcement ladder: private reminder → formal warning → temporary mute → permanent ban, scaled to severity and repetition. |
| Feedback | Track status with your one-time ticket (received / reviewing / replied / closed). Where third-party privacy is involved we return the outcome only, not the details. |
| Appeals | A sanctioned party can appeal through the same form, marking the title with "Appeal". |
Complaint form
Check progress
Full policy: CODE_OF_CONDUCT.md. Security policy: Security center and /.well-known/security.txt.