# Contributing to SnapOtter

Thanks for your interest in the project. Community feedback helps shape SnapOtter, and there are several ways to get involved.

## How to contribute

The best way to contribute is through [GitHub Issues](https://github.com/snapotter-hq/snapotter/issues):

- **Bug reports** - Found something broken? Open a bug report with steps to reproduce, your Docker setup, and what you expected to happen.
- **Feature requests** - Have an idea for a new tool or improvement? Describe the problem you want solved and why it matters to you.
- **Feedback** - Thoughts on the UI, workflow, documentation, or anything else? We want to hear it.

## Pull requests

We do not accept pull requests. All development is handled internally to maintain architectural consistency and code quality across the project.

If you've found a bug, please open an issue describing it rather than submitting a fix. If you have a suggestion for how something should work, describe it in a feature request. Your input is valuable even without a code contribution.

## Forking

You're welcome to fork the project for your own use under the terms of the [AGPLv3 license](LICENSE). The [Developer Guide](https://docs.snapotter.com/guide/developer) covers setup, architecture, and how to add new tools.

## Security

If you discover a security vulnerability, please report it privately through [GitHub Security Advisories](https://github.com/snapotter-hq/snapotter/security/advisories/new) rather than opening a public issue.