BettaGate takes security seriously. As an enterprise AI Gateway proxying credentials, routing model traffic, and enforcing security guardrails, we appreciate your efforts to responsibly disclose security vulnerabilities.
Only the latest release on the main branch receives active security updates and patches.
| Version | Supported |
|---|---|
| 0.1.x | ✅ |
| < 0.1 | ❌ |
Please do NOT report security vulnerabilities through public GitHub issues.
If you discover a security vulnerability in BettaGate (such as API key leakage, AES credential decryption bypass, authentication bypass, or PII deanonymization vulnerabilities), please report it privately:
- Email: Send details to
security@bettagate.com(or create a private Security Advisory on GitHub). - Details to include:
- Type of issue (e.g. credential leakage, auth bypass, injection risk)
- Step-by-step instructions to reproduce the vulnerability
- Proof-of-concept (PoC) code or requests if available
- Impact assessment
- Acknowledgement: We will acknowledge your report within 48 hours.
- Assessment: We will assess the severity and impact within 5 business days.
- Fix & Patch: We will prepare a security patch and release it promptly.
- Credit: We will publicly acknowledge your responsible disclosure in the security release notes (unless you prefer to remain anonymous).
Thank you for helping keep BettaGate and enterprise AI infrastructure safe!