This document outlines security procedures and general policies for the cosmpy project.
The following table shows which versions of cosmpy are currently being supported with security updates.
| Version | Supported |
|---|---|
< 1.0.0 |
✅ |
The cosmpy team and community take all security bugs in cosmpy seriously. We appreciate your efforts and responsible disclosure and will make every effort to acknowledge your contributions.
Report security bugs by emailing [email protected].
The lead maintainer will acknowledge your email within 48 hours, and will send a more detailed response within 48 hours indicating the next steps in handling your report. After the initial reply to your report, the security team will endeavour 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.
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 to PyPI.
If you have suggestions on how this process could be improved please submit a pull request.
We have a bug bounty program. Please report any security issues you find, or reach out to [email protected]. Please try to be as explicit as possible, describing all the steps and example code to reproduce the security issue.
Critical bug fixes will be backported to past major releases.
Please restrain from publicly discussing a potential security vulnerability. 🙊
It's better to discuss privately and try to find a solution first, to limit the potential impact as much as possible.