| Version | Supported |
|---|---|
| v0.1.x (alpha) | |
| v1.0.x (future) | ✅ Full support |
Please do NOT report security vulnerabilities through public GitHub Issues.
Instead, email: zhoujiankai1014@gmail.com
We will respond within 48 hours with:
- Confirmation of receipt
- An initial assessment
- A timeline for resolution
- Never commit API keys to the repository
- Use
.envfiles (gitignored) for local development - API keys stored in Run configs should be encrypted in production
- Authentication is enforced on all API routes via NextAuth.js
- v1.0.0 will include full NextAuth.js integration
- For production deployments, place AgentBench behind a reverse proxy with authentication
- PostgreSQL is used as the primary database
- Use strong passwords and TLS for production connections
- Regularly back up your database
- Dependencies are managed with pnpm and locked via
pnpm-lock.yaml - Dependabot/Renovate integration recommended for automated updates
- Run
pnpm auditperiodically to check for known vulnerabilities
- Run behind a reverse proxy (Nginx/Caddy) with HTTPS in production
- Set
WEBHOOK_SECRETto verify CI webhook requests - Use API keys with limited scopes for programmatic access
- Rotate secrets regularly
- Keep dependencies updated