Code of Conduct
Relevant source files
The following files were used as context for generating this wiki page:
The Code of Conduct for the Unified Security Scanner project establishes a pledge to provide a harassment-free experience for all participants. It outlines the standards of behavior expected from members, contributors, and leaders, regardless of their background, identity, or level of experience. The document serves as a foundational guide for maintaining an open, welcoming, and inclusive community environment.
This policy applies to all community spaces and instances where an individual is officially representing the project in public settings. Community leaders are tasked with the responsibility of clarifying and enforcing these standards to ensure the health and safety of the ecosystem.
Sources: CODE_OF_CONDUCT.md:3-13, CODE_OF_CONDUCT.md:52-59
Behavioral Standards
The project defines clear expectations for positive contributions and explicitly prohibits behavior that is considered unacceptable in a professional or community setting.
Positive Behavior
Contributors are encouraged to demonstrate empathy and kindness, respect differing opinions, and provide or accept constructive feedback gracefully. A focus on the collective best interest of the community is prioritized over individual goals.
Sources: CODE_OF_CONDUCT.md:17-26
Unacceptable Behavior
The following behaviors are strictly prohibited:
- Use of sexualized language or imagery.
- Trolling, insulting, or personal/political attacks.
- Public or private harassment.
- Publishing private information (doxxing) without permission.
- Any conduct inappropriate for a professional environment.
Sources: CODE_OF_CONDUCT.md:28-38
Enforcement Framework
The project utilizes a tiered enforcement ladder inspired by Mozilla’s guidelines to address violations. Community leaders have the authority to edit or reject contributions that do not align with these standards.
Enforcement Process Flow
The following diagram illustrates the reporting and investigation process for Code of Conduct violations:
This flowchart describes the progression from an initial report of unacceptable behavior to the final resolution determined by community leaders.
Sources: CODE_OF_CONDUCT.md:41-50, CODE_OF_CONDUCT.md:61-68
Community Impact Guidelines
Leaders follow specific consequences based on the severity and nature of the violation:
| Level | Impact Type | Consequence |
|---|---|---|
| 1. Correction | Unprofessional language/behavior | Private written warning and request for public apology. |
| 2. Warning | Single incident or series of actions | Warning with a specified period of prohibited interaction. |
| 3. Temporary Ban | Serious violation or sustained behavior | Temporary ban from all community interaction and communication. |
| 4. Permanent Ban | Pattern of violation or severe harassment | Permanent ban from all public interaction within the community. |
Sources: CODE_OF_CONDUCT.md:70-109
Reporting and Privacy
Instances of abusive or harassing behavior should be reported privately to the enforcement team at conduct@unified-scanner.dev. This is distinct from reporting security vulnerabilities, which are handled via security@unified-scanner.dev. Community leaders are contractually obligated to respect the privacy and security of the reporter throughout the investigation.
Sources: CODE_OF_CONDUCT.md:61-68, SECURITY.md:15-18
Leadership Responsibilities
Community leaders must:
- Maintain the security of the reporter.
- Provide reasons for moderation decisions when appropriate.
- Remove content (commits, code, wiki edits, issues) not aligned with the Code of Conduct.
Sources: CODE_OF_CONDUCT.md:41-50, CODE_OF_CONDUCT.md:67-68
Scope and Attribution
The Code of Conduct is active within all official community spaces and during official representation, such as using an official email address or social media account. This document is adapted from the Contributor Covenant, version 2.1.
Sources: CODE_OF_CONDUCT.md:52-59, CODE_OF_CONDUCT.md:113-116
The Unified Security Scanner project integrates this Code of Conduct into its broader contribution workflow, requiring all participants to read and follow it in all interactions to maintain the project's integrity and community health.
Sources: CONTRIBUTING.md:139-140