We release patches for security vulnerabilities. Currently supported versions:
| Version | Supported |
|---|---|
| 3.x | ✅ |
| < 3.0 | ❌ |
If you discover a security vulnerability within nx-go, please send an email to the maintainers or report it through GitHub Security Advisories.
Please do not report security vulnerabilities through public GitHub issues.
- Report: Submit a detailed report via GitHub Security Advisories or email the maintainers
- Acknowledgment: We will acknowledge receipt of your vulnerability report within 48 hours
- Assessment: We will assess the vulnerability and determine its impact and severity
- Fix: We will work on a fix and keep you informed of our progress
- Release: Once a fix is ready, we will release a security patch and publicly disclose the vulnerability
When reporting a vulnerability, please include:
- Type of vulnerability
- Full paths of source file(s) related to the vulnerability
- Location of the affected source code (tag/branch/commit or direct URL)
- Step-by-step instructions to reproduce the issue
- Proof-of-concept or exploit code (if possible)
- Impact of the issue, including how an attacker might exploit it
- A response acknowledging your report within 48 hours
- Regular updates on our progress
- Credit in the security advisory (unless you prefer to remain anonymous)
When using nx-go in your projects:
- Always use the latest stable version
- Keep your Go toolchain up-to-date
- Regularly run
nx migrate @nx-go/nx-goto stay current with security patches - Review dependency updates and security advisories
- Use
go mod tidyto keep your dependencies clean and up-to-date
- Security vulnerabilities will be disclosed publicly after a fix is released
- We will credit security researchers who responsibly disclose vulnerabilities (unless they prefer anonymity)
- We aim to release security patches within 30 days of receiving a valid report
Thank you for helping keep nx-go and its users safe!