The project currently supports the following versions for security updates:
| Version | Supported |
|---|---|
| Latest main branch | Yes |
| Previous released versions | Best effort or as announced |
We recommend always using the latest available version of the project and updating regularly.
If you discover a security vulnerability, please report it privately and responsibly.
Please do not open a public GitHub issue for security-sensitive reports.
Instead, contact the maintainer directly through GitHub:
- Open a private security advisory via the repository's Security tab, or
- Reach out through the repository owner contact information if available.
When reporting, include:
- A clear description of the vulnerability
- Steps to reproduce it
- Affected files, versions, or environments
- Any potential impact
- Suggested remediation ideas, if available
We aim to:
- Acknowledge reports within a reasonable timeframe
- Investigate and validate the issue
- Provide updates as needed during triage and remediation
- Coordinate a fix and disclosure plan when appropriate
We ask that security issues be kept confidential until a fix is ready or a coordinated disclosure plan is agreed upon. We appreciate responsible disclosure and will work with reporters to protect users while addressing the issue.
To help keep the project secure:
- Keep dependencies updated
- Review code changes for unsafe patterns
- Avoid committing secrets or sensitive credentials
- Use secure coding practices when handling user input and external data