BehaviorLock contributors must communicate with respect, challenge ideas without attacking people, disclose conflicts, protect private reports, and give credit for work. Harassment, discrimination, threats, sexualized attention, doxxing, deliberate humiliation, and retaliation are not accepted.
Technical disagreement is normal. Evidence, reproducible tests, and clear reasoning should decide engineering questions. Maintainers may pause a conversation that becomes personal or unsafe.
This policy currently applies to the BehaviorLock repository, issues, pull requests, GitHub Discussions, and private repository security reports. The project does not claim authority over unrelated or off platform spaces.
For a private conduct report, use the repository private reporting form and begin the title with Conduct report. Do not include vulnerability details unless the report also concerns security.
The maintainer will protect reporter privacy as far as reasonably possible, assess conflicts before acting, and choose a proportionate response. Responses may include a private warning, content removal, temporary participation limits, or a permanent ban.
BehaviorLock currently has one maintainer and therefore cannot offer independent internal adjudication. If a report concerns the maintainer or you do not trust the project channel, use GitHub's independent abuse reporting route for conduct covered by GitHub policy. The maintainer will not investigate or rule on a report in which they are the subject.
The project will add a monitored independent conduct contact before expanding this policy beyond GitHub or appointing a second maintainer. This limitation is stated openly so contributors can make an informed choice.
GitHub abuse and safety tools remain available for conduct outside the maintainer's control.