<p align="center">
  <a href="https://community.specterops.io/" target="_blank">
    <img alt="Community of SpecterOps - Creators of BloodHound" src=".github/GitHub-CONTRIB-Header.png" width="100%" style="max-width: 100%;">
  </a>
</p>

## 💡 How to Contribute
We welcome contributions from the community! Here's how you can help:
1. **Issues**: Feel free to open issues for bugs, feature requests, or questions
2. **Pull Requests**: Small improvements and bug fixes are welcome
3. **Discussions**: Use GitHub Discussions for general questions and ideas

## ⚙️ Contribution Process
1. Fork the repository
2. Create a feature branch
3. Make your changes with clear commit messages
4. Submit a pull request with a description of changes
5. The maintainer(s) will review and provide feedback

## 💬 Communication Channels
- **Primary**: GitHub Issues and Pull Requests
- **General Discussion**: GitHub Discussions
- **Security Issues**: [GitHub Private Vulnerability Reporting](SECURITY.MD) for security issues or private matters
- **Community Chat**: Slack message in the appropriate channel on [BloodHound Gang Slack](https://slack.specterops.io)

## 🕐 Response Times
Given the nature of how SpecterOps manages open-source contributions, response may be delayed by the maintainer. If you have a pressing matter and do not receive a response, first reach out via the communication channels mentioned above.

If the maintainer still does not reply, please contact us at community[@]specterops.io.

## 🤝 Code of Conduct
This project follows the [SpecterOps Community Code of Conduct](CODE_OF_CONDUCT.md). We expect all contributors to adhere to these guidelines to maintain a welcoming and inclusive community.

## ℹ️ Questions?
If you have questions about contributing, feel free to open a GitHub Discussion or reach out through our [community channels](https://community.specterops.io).
