# Security Policy
## Supported Versions
We release patches for security vulnerabilities for the following versions:
| 1.x.x | :white_check_mark: |
## Reporting a Vulnerability
We take the security of network-protocol seriously. If you believe you have found a security vulnerability, please report it to us as described below.
**Please do not report security vulnerabilities through public GitHub issues.**
Instead, please report them via email to: [jamesgober@users.noreply.github.com](mailto:jamesgober@users.noreply.github.com)
You should receive a response within 48 hours. If for some reason you do not, please follow up via email to ensure we received your original message.
Please include the following information in your report:
- Type of issue (e.g., buffer overflow, authentication bypass, etc.)
- Full paths of source file(s) related to the manifestation of the issue
- The location of the affected source code (tag/branch/commit or direct URL)
- Any special configuration required to reproduce the issue
- 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
This information will help us triage your report more quickly.
## Preferred Languages
We prefer all communications to be in English.
## Disclosure Policy
When we receive a security bug report, we will:
1. Confirm the problem and determine the affected versions
2. Audit code to find any potential similar problems
3. Prepare fixes for all supported releases
4. Release patched versions as soon as possible
## Comments on this Policy
If you have suggestions on how this process could be improved, please submit a pull request or open an issue to discuss.