chore: Add Contributor Covenant Code of Conduct

[unclesp1d3r]

This document outlines the Contributor Covenant Code of Conduct for community members, detailing pledges, standards of behavior, enforcement responsibilities, and consequences for violations.

[coderabbitai]

Summary by CodeRabbit

• Documentation
  • Added a Code of Conduct based on the Contributor Covenant.
  • Defines community standards, expected and unacceptable behaviors.
  • Outlines maintainers’ enforcement responsibilities and project scope.
  • Describes reporting procedures and confidentiality commitments.
  • Includes enforcement guidelines with escalating actions (Correction, Warning, Temporary Ban, Permanent Ban).
  • Provides attribution and external references.

Walkthrough

Added a new CODE_OF_CONDUCT.md documenting the Contributor Covenant, including pledge, standards, enforcement responsibilities, scope, enforcement process, enforcement guidelines, and attribution.

Changes

Cohort / File(s)	Summary of Changes
Project Governance CODE_OF_CONDUCT.md	Added Contributor Covenant Code of Conduct with sections for pledge, standards, responsibilities, scope, enforcement process, guidelines (Correction, Warning, Temporary Ban, Permanent Ban), and attribution.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

A bunny bows with courteous cheer,
New conduct codified, crystal-clear.
With gentle paws and friendly tone,
We keep the garden safely sown.
Hop by hop, we pledge and do—
Carrots, kindness, follow-through. 🥕✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The pull request title "chore: Add Contributor Covenant Code of Conduct" directly and accurately describes the main change in the changeset. The PR adds a single file, CODE_OF_CONDUCT.md, which contains the Contributor Covenant Code of Conduct, and the title clearly conveys this primary change. The title is concise, specific, and follows a conventional commit format with a clear scope prefix, making it easy for teammates to understand what was changed when scanning repository history.
Description Check	✅ Passed	The pull request description is clearly related to the changeset and provides relevant context about what is being added. It mentions the Contributor Covenant Code of Conduct and describes its key components including pledges, standards of behavior, enforcement responsibilities, and consequences for violations, all of which are present in the added CODE_OF_CONDUCT.md file. While concise, the description adequately conveys the nature and purpose of the change.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch unclesp1d3r-patch-1

---

🧪 Early access (Sonnet 4.5): enabled

We are currently testing the Sonnet 4.5 model, which is expected to improve code review quality. However, this model may lead to increased noise levels in the review comments. Please disable the early access features if the noise level causes any inconvenience.

Note:

• Public repositories are always opted into early access features.
• You can enable or disable early access features from the CodeRabbit UI or by updating the CodeRabbit configuration file.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

CODE_OF_CONDUCT.md (1)

117-119: Consider updating to Contributor Covenant version 2.1.

The document references version 2.0, but version 2.1 is the latest release of the Contributor Covenant. Updating ensures alignment with the most current community standards.

Apply this diff to update to version 2.1:

-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.0, available at
-https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between e90130d and 49866d7.

📒 Files selected for processing (1)

• CODE_OF_CONDUCT.md (1 hunks)

🧰 Additional context used

🪛 markdownlint-cli2 (0.18.1)

CODE_OF_CONDUCT.md

11-11: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

26-26: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

44-44: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

---

71-71: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

🔍 Remote MCP Linear

Based on my searches, I've found relevant context from Linear issues. The searches show that all the Linear issues found are related to EvilBit Labs projects, particularly the "Gold Digger" and "opnDossier" projects, not the "libmagic-rs" project mentioned in the PR. Let me search for information about the Contributor Covenant and Code of Conduct standards.

Now I have enough information to provide a comprehensive summary. Let me compile the findings.

Additional Context for PR Review: Code of Conduct Addition

Based on my research, I've found relevant information about this pull request to add the Contributor Covenant Code of Conduct to the libmagic-rs repository.

Contributor Covenant Code of Conduct - Background

The Contributor Covenant is the most widely adopted open source code of conduct in the world, created by Coraline Ada Ehmke. It is used in prominent projects including Linux, Ruby on Rails, Swift, Go, and JRuby, with signers including Google, Apple, Microsoft, Intel, Eclipse and GitLab. Since its initial release as an open source document in 2014, it has been adopted by over 100,000 open source projects.

Purpose and Benefits

The Contributor Covenant helps communities express their unique core values while setting clear expectations for how people should treat one another, and adopting it signals commitment to creating a welcoming and safe environment for everyone.

Repository Context: libmagic-rs

The repository mentioned in the PR (EvilBit-Labs/libmagic-rs) does not have related issues in the Linear workspace queried. The Linear workspace contains primarily Gold Digger and opnDossier projects under EvilBit Labs, but no specific libmagic-rs issues or documents.

EvilBit Labs Standards Context

From the Linear issues, I found that EvilBit Labs maintains comprehensive standards for their open source projects:

Standards Compliance Requirements:

• Multiple projects show a pattern of implementing comprehensive governance files including CODEOWNERS, SECURITY.md, and CONTRIBUTING.md
• Issue OPEN-40 specifically mentions adding standards compliance configuration files
• Issue OPEN-14 tracks "Standards Compliance Epic" showing organizational commitment to best practices

Relevance to Review

Positive Indicators:

1. Industry Standard: The Contributor Covenant is the most widely adopted code of conduct in open source
2. Organizational Alignment: EvilBit Labs demonstrates commitment to comprehensive project governance based on their other projects
3. Standard Practice: Adding a Code of Conduct is a recognized best practice for open source projects

Review Considerations:

1. Version: Verify the document uses the latest Contributor Covenant version (2.1 as of recent versions)
2. Contact Information: Ensure enforcement contacts are properly specified for the libmagic-rs project
3. Scope: Confirm the document properly defines community spaces and enforcement procedures relevant to this repository
4. Consistency: Check if this aligns with other EvilBit Labs projects' governance approaches

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: CodeQL Analyze
• GitHub Check: Analyze (rust)

🔇 Additional comments (2)

CODE_OF_CONDUCT.md (2)

61-63: Verify the enforcement contact email is active and monitored.

Ensure that support@evilbitlabs.io is an active, monitored email address that can handle code of conduct reports promptly and confidentially.

---

1-129: Excellent addition of the Contributor Covenant Code of Conduct.

The document is well-structured and includes all essential sections: pledge, standards, enforcement responsibilities, scope, enforcement process, and detailed guidelines. This aligns with EvilBit Labs' commitment to comprehensive project governance and establishes clear community expectations.

Based on learnings