Code of Conduct

Our commitment

This project exists to improve how organizations detect attacks. That requires people to disagree in public, often sharply, about technical matters. Everyone participating should be able to do so without personal hostility.

We commit to making participation harassment-free for everyone, regardless of experience level, background, identity or employer.

Expected behavior

• Argue with the idea. "This requirement is unachievable for a three-person team, here is why" is exactly the contribution this project needs.
• Bring evidence. Implementation experience outweighs assertion.
• Assume competence. Someone disagreeing with you has probably operated in an environment different from yours.
• Accept correction. Including the maintainers. The specification contains errors; finding them is a service.
• Respect vendor neutrality. Discuss platform capabilities factually. Promotional content is not a contribution.

Unacceptable behavior

• Personal attacks, insults or derogatory comments
• Harassment, public or private
• Sexualised language or imagery, or unwelcome advances
• Publishing others' private information without permission
• Sustained disruption of discussions
• Using the project as a marketing channel

Scope

This applies in all project spaces — issues, pull requests, discussions — and when representing the project publicly.

Enforcement

Report unacceptable behavior to the lead maintainer via the contact route in SECURITY.md. Reports are handled confidentially.

Maintainers will respond proportionately:

1. Correction. A private note explaining why the behavior was inappropriate.
2. Warning. A formal warning with consequences for continued behavior.
3. Temporary ban. From project spaces for a specified period.
4. Permanent ban. For sustained or severe violations.

Maintainers who do not enforce this in good faith may be removed from the project.

Attribution

Adapted from the Contributor Covenant, version 2.1.