As Gittxt is currently in v1.5.0, we aim to provide security updates for the latest release only.
| Version | Supported |
|---|---|
| 1.5.0 | ✅ Actively supported |
| < 1.4.1 | ❌ Not supported |
We are committed to ensuring the security of Gittxt and the safety of its users. If you discover a vulnerability, please follow the process below.
- Email sandeep.paidipati@gmail.com with the following:
- Description of the vulnerability
- Steps to reproduce
- Impact assessment (e.g., data leakage, remote execution, etc.)
- Suggested mitigation (if available)
Please do NOT file public issues for security vulnerabilities.
- We aim to acknowledge your report within 3 business days.
- After triage, remediation will typically occur within 30 days, depending on severity.
We practice responsible disclosure. We ask that reporters:
- Avoid publicly disclosing vulnerabilities prior to a confirmed patch release.
- Coordinate with us for coordinated disclosure timelines, if needed.
- We treat security issues with urgency.
- Critical vulnerabilities may lead to expedited releases.
- Credits will be given to researchers who responsibly disclose bugs (unless anonymity is requested).
Thank you for helping make Gittxt a safer project!