| Version | Supported |
|---|---|
| 1.x.x | ✅ |
| < 1.0 | ❌ |
We take security seriously. If you discover a security vulnerability, please follow these steps:
- Open a public GitHub issue
- Disclose the vulnerability publicly before it's fixed
- Exploit the vulnerability
- Email us at security@humantouch.dev (or open a private security advisory on GitHub)
- Include details:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Any suggested fixes
- Acknowledgment: Within 48 hours
- Initial Assessment: Within 1 week
- Resolution Timeline: Depends on severity
- Critical: 24-48 hours
- High: 1 week
- Medium: 2 weeks
- Low: Next release
- Never commit API keys to version control
- Use environment variables for all secrets
- Rotate keys regularly
- Use the minimum required permissions
- Always use HTTPS in production
- Set
NODE_ENV=production - Configure proper CORS settings
- Enable rate limiting
- Use strong JWT secrets (32+ characters)
# Production security settings
NODE_ENV=production
JWT_SECRET=<random-32+-character-string>
ALLOWED_API_KEYS=<your-whitelisted-keys>
DETECTOR_MODE=strictHumanTouch includes several security features:
- API Key Authentication: Bearer token validation
- Rate Limiting: Configurable request limits
- Input Validation: Text length and parameter checks
- Webhook Signatures: HMAC-SHA256 for callbacks
- Environment Separation: Dev/production mode detection
We appreciate responsible disclosure and will acknowledge security researchers who help improve HumanTouch's security.