Skip to content

Latest commit

 

History

History
40 lines (21 loc) · 1.82 KB

SECURITY.md

File metadata and controls

40 lines (21 loc) · 1.82 KB
Raw

Security Policy

Reporting a Security Issue

We take the security of Flavour Fusion seriously. We appreciate your efforts to responsibly disclose your findings, and we will work to promptly address and resolve any reported security issues.

To report a security issue, please follow these steps:

  1. DO NOT open an issue or a public discussion on the GitHub repository. Security issues should be reported privately.

  2. Contact us directly via email at [email protected].

  3. Include a detailed description of the vulnerability, including information about the affected components, potential impact, and any steps or proof-of-concept code.

  4. If you can, please provide us with a clear subject line, for example: "[Flavour Fusion] Security Issue - [Brief Description]".

  5. We will acknowledge your email within 24 hours and will work on confirming the issue.

  6. We will keep you informed about our progress in fixing the issue and our proposed timeline for a patch.

Responsible Disclosure

We kindly request that you follow responsible disclosure practices when reporting security issues. This includes:

  • Not disclosing the issue publicly until a fix has been developed and deployed.
  • Avoiding any attempts to gain unauthorized access to our systems or data.
  • Respecting the privacy and security of our users.

We greatly appreciate your cooperation in helping us ensure the security of Flavour Fusion.

Security Updates

To stay informed about security updates and patches, we recommend that you subscribe to our notifications or follow our repository's releases.

Attribution

We appreciate and acknowledge the contributions and reports from the security research community in making Flavour Fusion more secure.

Thank you for helping us keep Flavour Fusion safe and secure for everyone.