Skip to content

Security: Geijutsu/cherry

Security

SECURITY.md

Security Policy

Supported Versions

We release patches for security vulnerabilities. Currently supported versions:

Version Supported
latest
< 1.0

Reporting a Vulnerability

We take the security of our project seriously. If you believe you have found a security vulnerability, please report it to us as described below.

Where to Report

Please do NOT report security vulnerabilities through public GitHub issues.

Instead, please report them via email to: security@geijutsu.org

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

What to Include

Please include the following information in your report:

  • Type of issue (e.g., buffer overflow, SQL injection, cross-site scripting, etc.)
  • Full paths of source file(s) related to the manifestation of the issue
  • The 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

What to Expect

  • Acknowledgment of your report within 48 hours
  • Regular updates on our progress
  • Credit for your discovery (if desired) in our release notes
  • Notification when the vulnerability is fixed

Preferred Languages

We prefer all communications to be in English.

Security Update Policy

  • Security updates are released as soon as possible after verification
  • Security advisories are published via GitHub Security Advisories
  • Critical vulnerabilities are prioritized and released immediately
  • Users are notified through release notes and security advisories

Security Best Practices

When using this project:

  1. Always use the latest stable version
  2. Keep dependencies up to date
  3. Follow the principle of least privilege
  4. Enable all available security features
  5. Review and follow our security guidelines in the documentation

Disclosure Policy

  • We follow responsible disclosure practices
  • Security issues are fixed before public disclosure
  • Credit is given to security researchers (if desired)
  • Coordinated disclosure timeline is typically 90 days

Comments on this Policy

If you have suggestions on how this process could be improved, please submit a pull request.

There aren’t any published security advisories