| Version | Supported |
|---|---|
| 5.1.x | ✅ |
| < 4.0 | ❌ |
We take the security of our software seriously. If you believe you have found a security vulnerability, please follow these steps: Do not open a public issue.
To report a security vulnerability, please email a detailed description of the issue to johnny.chan@sydstu.catholic.edu.au. To help us address the risk quickly, please include as much information as possible, specifically: the exact steps to reproduce the exploit, the potential impact of the vulnerability, and any suggested fixes or mitigations you may have.
To ensure project integrity and maintain a verifiable audit trail of commits, GitHub Branch Rulesets were implemented. This prevented accidental deletions and forced a formal Pull Request workflow for all major logic updates. I have also included a MIT License to make this code into a proper professional workspace with copyrights.
Once we receive your report, our team will provide an acknowledgement within 48 hours. We will then begin a thorough investigation and may reach out to you for further details. Once a fix has been developed, we will notify you and release a patched version in accordance with our supported versions table.