Skip to content

Security: CyrusAuyeung/MuseMelody

Security

.github/SECURITY.md

Security Policy

Reporting a Vulnerability

If you believe you have found a security issue in MuseMelody, please do not open a public issue with full exploit details.

Instead:

  • Contact the repository owner privately if possible
  • Provide a clear description of the issue
  • Include reproduction steps and affected files or endpoints when relevant

We will review reports as soon as possible and determine the appropriate next steps.

What to Include

When reporting a security issue, please include:

  • A summary of the vulnerability
  • Steps to reproduce it
  • The potential impact
  • Any suggested remediation, if available

Scope

This includes, but is not limited to:

  • Sensitive data exposure
  • Unsafe file handling
  • Dependency-related risks
  • API misuse that could affect users or infrastructure

Disclosure

Please allow time for the issue to be investigated and fixed before disclosing technical details publicly.

There aren't any published security advisories