• Purpose
• Supported Versions
• Reporting a Vulnerability
  • What to Include
  • Response Process
• Security Measures
  • Code Review and Merging
  • Dependencies
  • Testing and CI/CD
• Disclosure Policy
• Security Updates
• Contact Information

This Security Policy outlines the measures and processes in place to ensure the security of Towerify and describes how security concerns can be reported by contributors and users.

Only the latest major version of Towerify receives regular patches and updates for security issues. Versions older than [N-1] are considered unsupported and may not receive security updates.

• Security issues should be reported via email to [email protected].
• Please do not report security vulnerabilities through public GitHub issues.

• A clear and concise description of the problem.
• Steps to reproduce the issue or a proof of concept (if applicable).
• Any relevant screenshots or supporting information.

• Reports will be acknowledged within 72 hours.
• The security team will review the issue and determine severity.
• Updates or patches will be issued as necessary.
• Public disclosure dates will be negotiated with the reporter.

All code submissions go through a peer review process to identify potential security issues before being merged into the main codebase.

All third-party libraries and dependencies are regularly reviewed for security vulnerabilities.

Automated security scans and testing are integrated into the Continuous Integration/Continuous Deployment (CI/CD) process.

To encourage responsible disclosure, we promise not to pursue legal action against individuals who report vulnerabilities in good faith and not exploit them.

We will make every effort to rectify the issue before any public disclosure, aiming to ensure that a fix is in place before the vulnerability is widely known.

Updates about security issues will be posted below or distributed via our mailing list. Users are encouraged to update their installations promptly to benefit from security fixes.

For any security concerns, please contact [email protected].