You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you discover a security vulnerability in LightShell, please report it responsibly.
12
+
13
+
**Do not open a public GitHub issue for security vulnerabilities.**
14
+
15
+
Instead, please send an email to **security@lightshell.dev** with:
16
+
17
+
1. A description of the vulnerability
18
+
2. Steps to reproduce the issue
19
+
3. The potential impact
20
+
4. Any suggested fixes (optional)
21
+
22
+
### What to expect
23
+
24
+
-**Acknowledgment**: We will acknowledge receipt of your report within 48 hours.
25
+
-**Assessment**: We will assess the vulnerability and determine its severity within 5 business days.
26
+
-**Fix timeline**: Critical vulnerabilities will be patched within 7 days. Other issues will be addressed in the next scheduled release.
27
+
-**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.
28
+
29
+
## Security Practices
30
+
31
+
- All GitHub Actions workflows use pinned SHA references to prevent supply-chain attacks.
32
+
- Dependencies are regularly audited with `govulncheck` and GitHub's Dependabot.
33
+
- CodeQL static analysis runs on every push and pull request.
34
+
- The OpenSSF Scorecard is monitored to maintain supply-chain security best practices.
35
+
36
+
## Scope
37
+
38
+
This security policy applies to the LightShell project repository and its official npm packages (`lightshell`, `create-lightshell`, and `@lightshell/*` platform packages).
0 commit comments