| Version | Supported |
|---|---|
| 0.1.x | ✅ |
Please do not open a public issue for security vulnerabilities.
Use GitHub's private reporting instead:
What qualifies:
- Remote code execution, path traversal, or SQL injection
- Secrets (API keys, Twilio credentials) leaking to logs, URLs, or other users
- Audio/transcript data leaving the machine without user consent
- Supply-chain or update-mechanism tampering
Expected response: acknowledgement within 7 days, coordinated disclosure after a fix ships.
- All AI provider keys travel in
x-goog-api-key-style headers — never in URLs — and must never be logged. - Twilio credentials live in
localStorageand are only sent toapi.twilio.com. - The app binds its media-stream and relay servers to
127.0.0.1only; public exposure happens exclusively through an explicit, user-enabled cloudflared tunnel.