Iván Eduardo Chavez Ayub
46 lines
1.5 KiB
Markdown
46 lines
1.5 KiB
Markdown
# Security Policy
|
|
|
|
## Supported Versions
|
|
|
|
We aim to support the most recent stable release of Warlock-Studio. Security updates and fixes are only guaranteed for:
|
|
|
|
| Version | Supported |
|
|
| ------- | --------- |
|
|
| 3.0.x | ✅ |
|
|
| 2.2.x | ✅ |
|
|
| 2.1.x | ✅ |
|
|
| 2.0.x | ✅ |
|
|
| 1.1.x | ✅ |
|
|
|
|
## Reporting a Vulnerability
|
|
|
|
If you discover a security vulnerability in Warlock-Studio or any of its integrated components, **please report it responsibly**:
|
|
|
|
- **Contact Email:** [negroayub97@gmail.com](mailto:negroayub97@gmail.com)
|
|
- **Do not** create a public GitHub issue to report security-related bugs.
|
|
|
|
Please include the following in your email:
|
|
|
|
- A detailed description of the vulnerability.
|
|
- Steps to reproduce the issue (if applicable).
|
|
- Your assessment of the potential impact.
|
|
|
|
We will acknowledge your report within **72 hours** and aim to provide a resolution or mitigation plan within **7 working days**, depending on severity.
|
|
|
|
## Scope
|
|
|
|
This security policy covers:
|
|
|
|
- The Warlock-Studio desktop application.
|
|
- AI models and third-party dependencies used within the app (to the extent they affect Warlock-Studio).
|
|
|
|
**Note:** Vulnerabilities in third-party tools such as Real-ESRGAN, FFmpeg, ONNX Runtime, etc., should ideally be reported upstream to their maintainers.
|
|
|
|
## Responsible Disclosure
|
|
|
|
We support responsible disclosure. Please give us time to investigate and fix issues before any public disclosure.
|
|
|
|
---
|
|
|
|
Thank you for helping make Warlock-Studio safer for everyone!
|