Skip to content

Security: SocialBeats/beats-interaction

Security

SECURITY.md

Security Policy

Thank you for taking the time to consider security in Socialbeats. We take the security of our project and its users seriously, and we appreciate your help in keeping it secure.

Reporting a Vulnerability

If you discover a security vulnerability in this project, please report it to us responsibly by following these steps:

1. Github Discussions

  1. Use Github Discussions: Go to the discussion board and report whatever you please. Bear in mind that you should be specific and clear about the vulnerability.

  2. Details to Include:

    • A detailed description of the vulnerability.
    • Steps to reproduce or a proof of concept (if applicable).
    • The version of the software you are testing.
    • Any other information that will help us understand and resolve the issue.

We will acknowledge your report as soon as possible, and we will work with you to resolve the issue. We aim to keep you updated throughout the process.

2. Using issue template

  1. Go to our github and create a security vulnerability report using specified template

Responsible Disclosure

We appreciate responsible disclosure. Please do not publicly disclose any vulnerabilities until we have had time to fix and release a patch. We will make a public statement once the issue has been resolved.

Security Updates

We will provide regular security updates to ensure that vulnerabilities are addressed in a timely manner. These updates will be made available through our usual release channels.

Our Commitment

We are committed to addressing vulnerabilities in the project as quickly as possible. Your help and cooperation in reporting issues responsibly allows us to protect users and maintain the integrity of the project.

Additional Resources

  • For more information on security practices, please refer to our [LICENSE] and [CONTRIBUTING.md] files.
  • For general security resources, you can refer to: OWASP.

Thank you for helping us keep Socialbeats secure!

There aren’t any published security advisories