Thank you for helping keep the DebateAI community and ecosystem secure. We take security vulnerabilities seriously and appreciate responsible, coordinated disclosure.
Security updates and patches are provided for the active release line of DebateAI-Landing Page:
| Version | Supported |
|---|---|
| 0.1.x | ✅ |
| < 0.1.0 | ❌ |
If you discover or suspect a security vulnerability in this project, please do not open a public GitHub issue.
Instead, report it privately through one of the following methods:
- GitHub Security Advisories (Preferred):
Submit a private advisory via GitHub Security Advisories. - Email Disclosure:
Contact the AOSSIE security team and project maintainers atsecurity@aossie.org.
To help us triage and resolve the issue quickly, please provide:
- A clear description of the vulnerability and its potential impact.
- Step-by-step instructions or a minimal proof-of-concept (PoC) to reproduce the behavior.
- Affected browser environments, versions, and deployment configurations.
- Any suggested mitigations or patches, if available.
We adhere to the following response timeline:
- Initial Acknowledgment: Within 5 business days of receiving your report.
- Triage & Assessment: Regular updates provided every 7 days until a resolution is planned.
- Remediation & Fix: Coordinated patch development and deployment to production.
- Public Disclosure: Conducted after a patch is deployed, crediting the researcher if desired.
We kindly ask that security researchers:
- Give us reasonable time to investigate and remediate reported issues before public disclosure.
- Avoid accessing, modifying, or deleting user or community data.
- Refrain from performing denial-of-service (DoS) attacks or automated scraping that degrades user experience.
Thank you for helping us maintain high security standards for open-source AI debate tools!