2.8 KiB
Security Policy for Continuwuity
This document outlines the security policy for Continuwuity. Our goal is to maintain a secure platform for all users, and we take security matters seriously.
Supported Versions
We provide security updates for the following versions of Continuwuity:
Version | Supported |
---|---|
Latest release | ✅ |
Main branch | ✅ |
Older releases | ❌ |
We may backport fixes to the previous release at our discretion, but we don't guarantee this.
Reporting a Vulnerability
Responsible Disclosure
We appreciate the efforts of security researchers and the community in identifying and reporting vulnerabilities. To ensure that potential vulnerabilities are addressed properly, please follow these guidelines:
- Contact members of the team over E2EE private message.
- Email the security team directly at security@continuwuity.org. This is not E2EE, so don't include sensitive details.
- Do not disclose the vulnerability publicly until it has been addressed
- Provide detailed information about the vulnerability, including:
- A clear description of the issue
- Steps to reproduce
- Potential impact
- Any possible mitigations
- Version(s) affected, including specific commits if possible
If you have any doubts about a potential security vulnerability, contact us via private channels first! We'd prefer that you bother us, instead of having a vulnerability disclosed without a fix.
What to Expect
When you report a security vulnerability:
- Acknowledgment: We will acknowledge receipt of your report.
- Assessment: We will assess the vulnerability and determine its impact on our users
- Updates: We will provide updates on our progress in addressing the vulnerability, and may request you help test mitigations
- Resolution: Once resolved, we will notify you and discuss coordinated disclosure
- Credit: We will recognize your contribution (unless you prefer to remain anonymous)
Security Update Process
When security vulnerabilities are identified:
- We will develop and test fixes in a private branch
- Security updates will be released as soon as possible
- Release notes will include information about the vulnerabilities, avoiding details that could facilitate exploitation where possible
- Critical security updates may be backported to the previous stable release
Additional Resources
This security policy was last updated on May 25, 2025.