We take the security of this project seriously. If you believe you have found a security vulnerability, please report it to us as described below. We appreciate your efforts to disclose it responsibly.
Please do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.
The preferred channel is private vulnerability reporting:
This creates a private communication channel between you and the maintainers. Alternatively, contact owners with the details via contact link or via contact option listed in profile.
You should receive an acknowledgment within 72 hours. If you do not, please follow up to confirm we received the original report.
Please include as much of the following as possible:
- Type of issue (e.g., injection, authentication flaw, memory corruption)
- Full paths of source file(s) related to the manifestation
- The location of the affected code (tag/branch/commit or direct URL)
- Step-by-step instructions to reproduce the issue
- Proof-of-concept or exploit code (if possible)
- Impact of the issue, including how an attacker might exploit it
- Any special configuration required to reproduce the issue
| Version | Supported |
|---|---|
| v3.0.0.0 | Yes |
| < v3.0.0.0 | No |
Only the latest major release receives security fixes.
Reports are handled privately, and details are published only after a fix is available. Please give us a reasonable amount of time to remediate before disclosing the issue publicly.
The following are explicitly out of scope:
- Issues in dependencies, report those to the respective projects
- Automated scanner output without a demonstrated, reproducible impact
- Social engineering, denial of service, or physical attacks
- Do not open a public issue, including on other repositories, describing the vulnerability
- Do not disclose details publicly before a fix is released
- Do not test against deployments you do not own