We currently support the following versions with security updates:
| Version | Supported |
|---|---|
| 1.3.0 | ✅ |
| < 1.3.0 | ❌ |
We take the security of openrouter-go seriously. If you discover a security vulnerability, please follow these steps:
- Do NOT open a public GitHub issue for security vulnerabilities
- Report security issues through GitHub Security Advisories
- Alternatively, you can email the maintainer directly through GitHub
When reporting a vulnerability, please include:
- Description of the vulnerability
- Steps to reproduce the issue
- Potential impact
- Suggested fix (if any)
- Your contact information for follow-up
- Initial Response: We aim to acknowledge your report within 48 hours
- Status Updates: You can expect updates on the progress every 5-7 days
- Resolution: We will work to resolve confirmed vulnerabilities as quickly as possible, typically within 30 days for moderate to high severity issues
-
Accepted Vulnerabilities: If your report is accepted, we will:
- Work on a fix in a private branch
- Credit you in the security advisory (unless you prefer to remain anonymous)
- Notify you when the fix is released
- Publish a security advisory with details after the fix is deployed
-
Declined Reports: If we determine the report is not a security vulnerability, we will:
- Explain our reasoning
- Suggest alternative channels if the issue is still valid but not security-related
When using this library:
- API Key Security: Never commit your OpenRouter API keys to version control
- Environment Variables: Store API keys in environment variables or secure secret management systems
- Dependencies: Keep the library updated to the latest version for security patches
- Input Validation: Always validate and sanitize user input before passing to API calls
- Error Handling: Properly handle errors to avoid leaking sensitive information
We follow responsible disclosure practices:
- Security issues are fixed privately before public disclosure
- We coordinate with reporters on disclosure timing
- Security advisories are published after fixes are available
- We credit security researchers who report issues (with permission)
Thank you for helping keep openrouter-go secure!