| Version | Supported |
|---|---|
| latest | Yes |
If you discover a security vulnerability in LightShell, please report it responsibly.
Do not open a public GitHub issue for security vulnerabilities.
Instead, please send an email to security@lightshell.dev with:
- A description of the vulnerability
- Steps to reproduce the issue
- The potential impact
- Any suggested fixes (optional)
- Acknowledgment: We will acknowledge receipt of your report within 48 hours.
- Assessment: We will assess the vulnerability and determine its severity within 5 business days.
- Fix timeline: Critical vulnerabilities will be patched within 7 days. Other issues will be addressed in the next scheduled release.
- Disclosure: We will coordinate with you on public disclosure timing. We ask that you allow us a reasonable window to release a fix before any public disclosure.
- All GitHub Actions workflows use pinned SHA references to prevent supply-chain attacks.
- Dependencies are regularly audited with
govulncheckand GitHub's Dependabot. - CodeQL static analysis runs on every push and pull request.
- The OpenSSF Scorecard is monitored to maintain supply-chain security best practices.
This security policy applies to the LightShell project repository and its official npm packages (lightshell, create-lightshell, and @lightshell/* platform packages).