This Security Policy outlines the measures and procedures in place to ensure the security of the LongTrainer project, detailing how security issues are handled by the project team and providing guidelines for researchers or users who discover a security issue.
Security updates will be applied to only the most recent version of LongTrainer. The following table shows which versions are currently being supported with security updates:
| Version | Supported |
|---|---|
| 0.2.x | ✅ |
| < 0.2.x | ❌ |
If you believe you have found a security vulnerability in LongTrainer, we encourage you to let us know right away. We will investigate all legitimate reports and do our best to quickly fix the problem. Please follow these steps for reporting:
Confidentiality: Send your report privately to our dedicated security email at technology@endevsols.com. Please do not report security vulnerabilities through public GitHub issues, discussions, or other public channels. Information: Provide as much information as possible about the vulnerability, including: The version of LongTrainer affected. A detailed description of the vulnerability. Step-by-step instructions to reproduce the issue if possible. Any possible impacts of the vulnerability. Communication: After submitting your report, you will receive an acknowledgment within 48 hours. We will then keep you informed of the progress towards a fix and full announcement, and may ask for additional information or guidance.
The LongTrainer team is committed to maintaining the security of our software and conducts regular security reviews and updates. However, no technology can be completely secure, and so by using LongTrainer, you acknowledge the potential risks involved.
When we learn of a security issue, we will:
Assess the vulnerability to determine the severity of the impact. Patch the issue within a reasonable timeframe depending on the severity. Release an updated version of LongTrainer as soon as the patch is ready. Publicly disclose the details of the vulnerability to ensure that all users are aware and can protect themselves. Disclosure timing may depend on the severity and complexity of the issue.
Users of LongTrainer are encouraged to follow these best practices to ensure security:
Always use the latest version of LongTrainer. Monitor our repository for announcements regarding security updates. Configure security features such as encryption and access controls as recommended in our documentation.
We encourage the community to get involved in ensuring the security of LongTrainer. Contributions to security, including enhancement suggestions, code reviews, and documentation improvements, are always welcome and can be submitted via GitHub pull requests.
- Contact For any security-related questions or concerns, please email us directly at technology@endevsols.com.