Versions of Genie.jl currently being supported with security updates.
| Version | Supported |
|---|---|
| >= 4.16.x | ✔ |
| <= 4.15.x | x |
This document outlines security procedures and general policies for the Genie project.
The Genie team and community take all security bugs in Genie seriously. Thank you for improving the security of Genie. We appreciate your efforts and responsible disclosure and will make every effort to acknowledge your contributions.
Report security bugs by emailing the lead maintainer on following email: [email protected] with subject as followed:
**[SECURITY Genie.jl] followed with subject of security bug**
To ensure the timely response to your report, please ensure that the entirety of the report is contained within the email body and not solely behind a web link or an attachment.
The lead maintainer will acknowledge your email within 42 hours, and will send a more detailed response within 42 hours indicating the next steps in handling your report. After the initial reply to your report, the security team will endeavor to keep you informed of the progress towards a fix and full announcement, and may ask for additional information or guidance.
Report security bugs in third-party modules to the person or team maintaining the module with cc'ed [email protected] if Genie.jl is using the module as one of the dependencies
When the security team receives a security bug report, they will assign it to a primary handler. This person will coordinate the fix and release process, involving the following steps:
- Confirm the problem and determine the affected versions.
- Audit code to find any potential similar problems.
- Prepare fixes for all releases still under maintenance. These fixes will be released as fast as possible and will be available with latest tagged Genie version and announced on Genie's twitter and Genie's Discord #announcement channel.
If you have suggestions on how this process could be improved please submit a pull request.