| Version | Supported |
|---|---|
| Latest | β Yes |
| < 1.0 | β No |
We take security seriously. If you discover a security vulnerability, please follow these guidelines:
DO NOT open a public GitHub issue for critical security vulnerabilities.
Instead, please report privately via one of these methods:
-
GitHub Security Advisories (Recommended)
- Go to the Security tab
- Click "Report a vulnerability"
- Fill out the private security advisory form
-
Email
- Send details to: gaikwadsiddharth039@gmail.com
- Use subject line:
[SECURITY] Brief description
- Description of the vulnerability
- Steps to reproduce the issue
- Potential impact assessment
- Suggested fix (if you have one)
- Your contact information for follow-up
| Action | Timeline |
|---|---|
| Initial Response | Within 48 hours |
| Status Update | Within 7 days |
| Fix Timeline | Based on severity |
We appreciate security researchers who help keep our community safe:
- Credit in release notes (with permission)
- Acknowledgment in our security hall of fame
- Potential bug bounty (for critical issues)
For non-critical security concerns that can be discussed publicly, you may use our Security Issue Template.
Thank you for helping keep siddcn secure! π‘οΈ