Skip to content

Security: techthoughts2/Catesta

Security

.github/SECURITY.md

Security Policy

Reporting a Vulnerability

If you discover a vulnerability in Catesta, please follow the following process:

  1. Open a generic bug issue advising you have discovered a vulnerability.

    • Avoid sharing specifics or details of the vulnerability in an open GitHub issue.
  2. A repo owner will reach out to you to establish a private form of communication.

  3. We will evaluate the vulnerability and, if necessary, release a fix or mitigating steps to address it. We will contact you to let you know the outcome, and will credit you in the report.

    Please do not disclose the vulnerability publicly until a fix is released!

  4. Once we have either a) published a fix, or b) declined to address the vulnerability for whatever reason, you are free to publicly disclose it.

There aren’t any published security advisories