Skip to content

Security: hivellm/rulebook

Security

SECURITY.md

Security Policy

Supported Versions

Version Supported
0.4.x
0.3.x
0.2.x
< 0.2

Reporting a Vulnerability

Please do not report security vulnerabilities through public GitHub issues.

Instead, please report them via email to Your Name.

You should receive a response within 48 hours. If for some reason you do not, please follow up to ensure we received your original message.

What to Include

Please include the following information:

  • Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
  • Full paths of source file(s) related to the issue
  • Location of the affected source code (tag/branch/commit or direct URL)
  • Any special configuration required to reproduce the issue
  • Step-by-step instructions to reproduce the issue
  • Proof-of-concept or exploit code (if possible)
  • Impact of the issue, including how an attacker might exploit it

Disclosure Policy

When we receive a security bug report, we will:

  1. Confirm the problem and determine affected versions
  2. Audit code to find any similar problems
  3. Prepare fixes for all supported versions
  4. Release new versions ASAP

Security Update Process

Security updates will be released as:

  • Critical: Within 24 hours
  • High: Within 7 days
  • Medium: Within 30 days
  • Low: Next regular release

Comments

We appreciate your efforts to responsibly disclose your findings and will make every effort to acknowledge your contributions.


For security concerns, contact Your Name

There aren’t any published security advisories