docs: add community governance files

* docs: Add CODE_OF_CONDUCT.md and SECURITY.md

Adds standard community health files to the project.

- CODE_OF_CONDUCT.md is based on the Contributor Covenant v3.0.
- SECURITY.md provides a clear policy for responsible vulnerability reporting.

* docs: add codeowners and issue templates

Author: aureliuscanon

.github/CODEOWNERS

@@ -0,0 +1,2 @@
+# Default owner for the entire repository
+* @aureliuscanon

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,29 @@
+---
+name: Bug Report
+about: Create a report to help us improve Privlog
+title: "[BUG] "
+labels: bug
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Code snippet to scan: `...`
+2. Command you ran: `privlog ...`
+3. What you saw: `...`
+4. What you expected to see: `...`
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Environment (please complete the following information):**
+ - OS: [e.g. macOS, Windows, Linux]
+ - Python version: [e.g. 3.9]
+ - Privlog version: [e.g. 0.2.1]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature Request
+about: Suggest an idea for Privlog
+title: "[FEAT] "
+labels: enhancement
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. "I'm always frustrated when..."
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

CODE_OF_CONDUCT.md

@@ -0,0 +1,90 @@
+# Contributor Covenant 3.0 Code of Conduct
+
+## Our Pledge
+
+We pledge to make our community welcoming, safe, and equitable for all.
+
+We are committed to fostering an environment that respects and promotes the dignity, rights, and contributions of all individuals, regardless of characteristics including race, ethnicity, caste, color, age, physical characteristics, neurodiversity, disability, sex or gender, gender identity or expression, sexual orientation, language, philosophy or religion, national or social origin, socio-economic position, level of education, or other status. The same privileges of participation are extended to everyone who participates in good faith and in accordance with this Covenant.
+
+## Encouraged Behaviors
+
+While acknowledging differences in social norms, we all strive to meet our community’s expectations for positive behavior. We also understand that our words and actions may be interpreted differently than we intend based on culture, background, or native language.
+
+With these considerations in mind, we agree to behave mindfully toward each other and act in ways that center our shared values, including:
+
+- Respecting the purpose of our community, our activities, and our ways of gathering.
+- Engaging kindly and honestly with others.
+- Respecting different viewpoints and experiences.
+- Taking responsibility for our actions and contributions.
+- Gracefully giving and accepting constructive feedback.
+- Committing to repairing harm when it occurs.
+- Behaving in other ways that promote and sustain the well-being of our community.
+
+## Restricted Behaviors
+
+We agree to restrict the following behaviors in our community. Instances, threats, and promotion of these behaviors are violations of this Code of Conduct.
+
+- Harassment. Violating explicitly expressed boundaries or engaging in unnecessary personal attention after any clear request to stop.
+- Character attacks. Making insulting, demeaning, or pejorative comments directed at a community member or group of people.
+- Stereotyping or discrimination. Characterizing anyone’s personality or behavior on the basis of immutable identities or traits.
+- Sexualization. Behaving in a way that would generally be considered inappropriately intimate in the context or purpose of the community.
+- Violating confidentiality. Sharing or acting on someone’s personal or private information without their permission.
+- Endangerment. Causing, encouraging, or threatening violence or other harm toward any person or group.
+- Behaving in other ways that threaten the well-being of our community.
+
+## Other Restrictions
+
+- Misleading identity. Impersonating someone else for any reason, or pretending to be someone else to evade enforcement actions.
+- Failing to credit sources. Not properly crediting the sources of content you contribute.
+- Promotional materials. Sharing marketing or other commercial content in a way that is outside the norms of the community.
+- Irresponsible communication. Failing to responsibly present content which includes, links or describes any other restricted behaviors.
+
+## Reporting an Issue
+
+Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm.
+
+When an incident does occur, it is important to report it promptly. To report a possible violation, please contact the repository maintainer directly or open a confidential GitHub issue.
+
+Community Moderators take reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. Community Moderators will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution.
+
+## Addressing and Repairing Harm
+
+If an investigation by the Community Moderators finds that this Code of Conduct has been violated, the following enforcement ladder may be used to determine how best to repair harm, based on the incident’s impact on the individuals involved and the community as a whole. Depending on the severity of a violation, lower rungs on the ladder may be skipped.
+
+### Warning
+
+- **Event:** A violation involving a single incident or series of incidents.
+- **Consequence:** A private, written warning from the Community Moderators.
+- **Repair:** Examples of repair include a private written apology, acknowledgement of responsibility, and seeking clarification on expectations.
+
+### Temporarily Limited Activities
+
+- **Event:** A repeated incidence of a violation that previously resulted in a warning, or the first incidence of a more serious violation.
+- **Consequence:** A private, written warning with a time-limited cooldown period designed to underscore the seriousness of the situation and give the community members involved time to process the incident. The cooldown period may be limited to particular communication channels or interactions with particular community members.
+- **Repair:** Examples of repair may include making an apology, using the cooldown period to reflect on actions and impact, and being thoughtful about re-entering community spaces after the period is over.
+
+### Temporary Suspension
+
+- **Event:** A pattern of repeated violation which the Community Moderators have tried to address with warnings, or a single serious violation.
+- **Consequence:** A private written warning with conditions for return from suspension. In general, temporary suspensions give the person being suspended time to reflect upon their behavior and possible corrective actions.
+- **Repair:** Examples of repair include respecting the spirit of the suspension, meeting the specified conditions for return, and being thoughtful about how to reintegrate with the community when the suspension is lifted.
+
+### Permanent Ban
+
+- **Event:** A pattern of repeated code of conduct violations that other steps on the ladder have failed to resolve, or a violation so serious that the Community Moderators determine there is no way to keep the community safe with this person as a member.
+- **Consequence:** Access to all community spaces, tools, and communication channels is removed. In general, permanent bans should be rarely used, should have strong reasoning behind them, and should only be resorted to if working through other remedies has failed to change the behavior.
+- **Repair:** There is no possible repair in cases of this severity.
+
+This enforcement ladder is intended as a guideline. It does not limit the ability of Community Managers to use their discretion and judgment, in keeping with the best interests of our community.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public or other spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Attribution
+
+This Code of Conduct is adapted from the Contributor Covenant, version 3.0, permanently available at https://www.contributor-covenant.org/version/3/0/.
+
+Contributor Covenant is stewarded by the Organization for Ethical Source and licensed under CC BY-SA 4.0. To view a copy of this license, visit https://creativecommons.org/licenses/by-sa/4.0/
+
+For answers to common questions about Contributor Covenant, see the FAQ at https://www.contributor-covenant.org/faq. Translations are provided at https://www.contributor-covenant.org/translations. Additional enforcement and community guideline resources can be found at https://www.contributor-covenant.org/resources. The enforcement ladder was inspired by the work of Mozilla’s code of conduct team.

SECURITY.md

@@ -0,0 +1,53 @@
+# Security Policy
+
+## Supported Versions
+
+Privlog is currently in early development. Security fixes will generally be applied to the latest released version.
+
+Users are encouraged to update to the most recent version available on PyPI.
+
+## Reporting a Vulnerability
+
+If you believe you have discovered a security vulnerability in Privlog, please report it responsibly.
+
+Please **do not publicly disclose the issue immediately**.
+
+Instead, report the issue through one of the following channels:
+
+* Open a **GitHub Security Advisory** (preferred)
+* Contact the repository maintainer through GitHub
+
+Include the following information if possible:
+
+* A clear description of the issue
+* Steps to reproduce the behavior
+* Example code or logs demonstrating the issue
+* The version of Privlog affected
+* Any suggested mitigation or fix
+
+## Scope of Security Reports
+
+Security reports may include:
+
+* Vulnerabilities in dependency handling
+* Packaging or distribution issues
+* Bugs that cause sensitive data detection to fail unexpectedly
+* Logic errors in rule evaluation that may cause false negatives
+* Supply-chain or build integrity concerns
+
+Please note that Privlog is a **static analysis tool** designed to assist developers in identifying potentially sensitive logging patterns. It does not guarantee complete detection of all possible data leaks.
+
+## Disclosure Process
+
+After a report is received:
+
+1. The issue will be reviewed and validated.
+2. A fix will be developed if the report is confirmed.
+3. A patch release will be issued when appropriate.
+4. Public disclosure may occur after a fix is available.
+
+Responsible disclosure helps protect users and maintain the integrity of the project.
+
+## Acknowledgements
+
+We appreciate responsible security research and the efforts of contributors who help improve the safety and reliability of the project.