If you discover a security vulnerability within CodeHunts, please send an email to security@codehuntspk.com. All security vulnerabilities will be promptly addressed.
Please do not publicly disclose the issue until it has been addressed by our team.
- Report is received and assigned to a primary handler
- Problem is confirmed and affected versions are determined
- Code is audited to find similar problems
- Fixes are prepared for all supported versions
- Fixes are released and security advisory is published
- Security updates are released as soon as possible
- Users are notified via email and GitHub Security Advisories
- CVE identifiers are requested for critical vulnerabilities
When deploying CodeHunts:
- Environment Variables: Never commit
.envfiles - Dependencies: Keep dependencies updated
- HTTPS: Always use HTTPS in production
- API Keys: Rotate API keys regularly
- Access Control: Implement proper authentication/authorization
- Input Validation: Validate and sanitize all user inputs
- Error Handling: Don't expose sensitive information in errors
| Version | Supported |
|---|---|
| 1.x.x | ✅ |
| < 1.0 | ❌ |
- All dependencies are up to date
- No hardcoded secrets in code
- Input validation implemented
- CSRF protection enabled
- XSS prevention measures in place
- SQL injection prevention (if applicable)
- Rate limiting implemented
- Logging and monitoring configured
Thank you for helping keep CodeHunts secure!