Skip to content

Security: EQuBitC18/Tezrisat

Security

SECURITY.md

Security Policy

Reporting Security Vulnerabilities

Security matters. If you find a vulnerability, thank you for reporting it responsibly.

How to Report

Please do not report security vulnerabilities through public GitHub issues.

Instead, please report security vulnerabilities by emailing:

What to Include

When reporting a vulnerability, include:

  1. Description: A clear description of the vulnerability
  2. Steps to Reproduce: Detailed steps to reproduce the issue
  3. Impact: Potential impact and severity of the vulnerability
  4. Affected Versions: Which versions are affected
  5. Mitigation: Any suggested fixes or workarounds
  6. Contact Information: How we can reach you for follow-up

Our Process

  1. Acknowledgment: We'll acknowledge receipt as soon as possible
  2. Investigation: We'll investigate and validate the report
  3. Fix Development: We'll develop and test a fix
  4. Disclosure: We'll coordinate disclosure with you
  5. Release: We'll release the fix and publish an advisory

Guidelines

  • Responsible Disclosure: Please allow us time to fix the issue before public disclosure
  • No Public Discussion: Please avoid discussing the vulnerability publicly until we've addressed it
  • Good Faith: Reports should be made in good faith and not for malicious purposes

Contact

For questions about this policy or security-related concerns:

There aren’t any published security advisories