| | 1 | + | # Security Policy |
| | 2 | + | |
| | 3 | + | ## Supported Versions |
| | 4 | + | |
| | 5 | + | | Version | Supported | |
| | 6 | + | | :-----: | :----------------: | |
| | 7 | + | | 2.x | :white_check_mark: | |
| | 8 | + | | 1.x | :x: | |
| | 9 | + | |
| | 10 | + | ## Reporting a Vulnerability |
| | 11 | + | |
| | 12 | + | If you believe you have found a security vulnerability in this repository, please report it to me through coordinated disclosure. |
| | 13 | + | |
| | 14 | + | **Please do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.** |
| | 15 | + | |
| | 16 | + | Instead, please send an email to xjasonlyu[@]gmail.com. |
| | 17 | + | |
| | 18 | + | Please include as much of the information listed below as you can to help me better understand and resolve the issue: |
| | 19 | + | |
| | 20 | + | * The type of issue (e.g., buffer overflow, payload attack) |
| | 21 | + | * Full paths of source file(s) related to the manifestation of the issue |
| | 22 | + | * The location of the affected source code (tag/branch/commit or direct URL) |
| | 23 | + | * Any special configuration required to reproduce the issue |
| | 24 | + | * Step-by-step instructions to reproduce the issue |
| | 25 | + | * Proof-of-concept or exploit code (if possible) |
| | 26 | + | * Impact of the issue, including how an attacker might exploit the issue |
| | 27 | + | |
| | 28 | + | This information will help me triage your report more quickly. |
| | 29 | + | |
