Definitely Secure Studio is committed to a professional, respectful, and constructive environment across repositories, issues, pull requests, reviews, and other project spaces.
- Treat people with respect and assume good faith while evaluating work on its merits.
- Give specific, actionable feedback and accept correction without hostility.
- Respect privacy, confidentiality, creative boundaries, and spoiler controls.
- Make space for different experience levels, backgrounds, identities, and communication styles.
- Disclose conflicts of interest and step back when impartial review is not possible.
- Harassment, discrimination, threats, stalking, sexualized conduct, or personal attacks.
- Deliberate intimidation, sustained disruption, or publishing another person's private information.
- Sharing credentials, private lore, unreleased material, vulnerability details, or confidential reports outside their approved channels.
- Plagiarism, knowingly false provenance claims, or attempts to bypass licensing and review controls.
- Retaliation against someone who raises a concern in good faith.
Do not report conduct concerns in a public issue. Use an established private
Studio contact or the private reporting route described by the affected
repository's SECURITY.md. If the report concerns a maintainer, direct it to an
organization owner who is not involved.
Maintainers will limit access to reports, protect confidentiality as far as practical, hear affected parties, preserve relevant evidence, and respond in proportion to severity and pattern. Responses may include clarification, content removal, a warning, temporary participation limits, removal of access, or a permanent ban. Immediate action may be taken to protect people or private material. Good-faith reports will not result in retaliation.
This code applies whenever a person is representing Definitely Secure Studio or participating in a Studio-managed project space.