# Security Policy for gitbook2text
We take security seriously ! If you find a vulnerability, please report it **privately** so we can fix it before it affects users.
---
## How to Report a Vulnerability
* **Email:** [maximilien.grzeczka@epitech.eu](mailto:maximilien.grzeczka@epitech.eu)
* Include:
* Description of the issue
* Steps to reproduce
* GitBook version or environment details
* Possible impact
We aim to acknowledge all reports within **96 hours**.
---
## Supported Versions
* **v0.3.x** – current stable version (receives all updates)
* **v0.2.x** – legacy support (critical fixes only)
Older versions may not receive fixes. Upgrade to the latest version for security.
---
## Security Tips for Users
* Always use the **latest release**.
* Be careful when crawling untrusted GitBooks.
* Consider running the CLI in an **isolated environment**.
* Verify downloaded content before using it in automated pipelines.
---
## Fix Process
1. Confirm and assess the vulnerability.
2. Fix privately.
3. Release a patched version and update the changelog.
4. Notify users via GitHub releases.
---
For non-security issues (bugs, features, documentation), please use [GitHub Issues](https://github.com/Maki-Grz/gitbook2text/issues).