If you discover a security vulnerability in Homerun, please report it responsibly.
Do not open a public issue. Instead, email the maintainer directly or use GitHub's private vulnerability reporting feature.
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if you have one)
- Acknowledgment: Within 48 hours
- Assessment: Within 1 week
- Fix: Depends on severity, but critical issues are prioritized
The following are in scope:
- Backend API endpoints (injection, authentication bypass, etc.)
- Private key or credential exposure
- WebSocket vulnerabilities
- Dependencies with known CVEs
The following are out of scope:
- Polymarket platform vulnerabilities (report those to Polymarket directly)
- Issues that require physical access to the host machine
- Social engineering
- Never commit secrets — keep private keys and API secrets out of version control
- Use paper trading mode first — verify the system works before enabling live trading
- Set conservative limits — use the Settings UI to cap trade sizes and daily volume
- Keep dependencies updated — run
pip install --upgrade -r requirements.txtandnpm updateregularly - Run behind a firewall — the dashboard and API are not designed for public internet exposure without additional authentication