The security of Mr Sweet is important to us. This document outlines our security policy and the measures we take to protect the project and its users.

Only the latest version of Mr Sweet is currently supported. If you're using an older version, we recommend upgrading to the latest version to ensure that you have the most up-to-date security fixes and improvements. Older versions may receive security updates on a case-by-case basis.

If you discover a vulnerability in Mr Sweet, please report it to us as soon as possible. To report a vulnerability, please fill out a Github advisory with the following information:

• A detailed description of the vulnerability, including steps to reproduce it
• The version of Mr Sweet you're using
• Any relevant error messages or logs
• Any other information that may be helpful in understanding and addressing the vulnerability

We will review your report and respond as soon as possible. If the vulnerability is confirmed, we will work to address it as quickly as possible.

We currently do not have a bug bounty program.

We take the following measures to keep Mr Sweet and its users secure:

• Regularly updating dependencies to ensure that we're using the latest, most secure versions
• Reviewing code changes to ensure that they don't introduce security vulnerabilities
• Following secure coding practices and guidelines
• Monitoring logs and alerts for potential security issues

Thank you for helping us keep Mr Sweet and its users secure. If you have any questions or concerns, please don't hesitate to contact us using Github Issues