| Version | Supported |
|---|---|
| 2.x | ✅ Yes |
| 1.x | ❌ No |
Do NOT open public GitHub issues for security vulnerabilities.
Please report security vulnerabilities responsibly:
-
Email: maintainer-email@example.com
-
Include:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if any)
-
Allow 90 days for review and fix before public disclosure
- Keep dependencies updated: Run
npm updateregularly - Never commit
.envfiles: Use.env.examplefor templates - Rotate API keys if compromised
- Use strong passwords for WhatsApp accounts
- Monitor logs for suspicious activity
- Never log sensitive data (API keys, tokens, etc)
- Validate all user inputs
- Sanitize error messages (don't leak internal details)
- Use environment variables for configuration
- Keep dependencies current
Before each release:
- Update dependencies (
npm audit) - Run security tests
- Review error handling
- Verify no secrets in code
- Update CHANGELOG
- Test with new Node.js LTS
- Report received → Confirm within 48 hours
- Investigation → Understand scope and impact
- Fix development → Create patch in private branch
- Review → Internal security review
- Release → Publish security update
- Disclosure → Public announcement with details
- WhatsApp session stored in
.wwebjs_auth/(keep secure) - API keys required for Gemini and Jina (validate access)
- Puppeteer runs browser (ensure safe deployment)
- URL validation uses regex (not foolproof)
Security issues: [maintainer-email@example.com] General inquiries: See SUPPORT.md
Thank you for helping keep Noria secure!