If you believe you have discovered a security vulnerability, please report it privately.

Do not disclose suspected vulnerabilities in public issues, pull requests, discussions, or other public channels.

Use the repository's GitHub Security tab and select the private vulnerability reporting option, if available.

If private vulnerability reporting is unavailable, contact the repository maintainer through an established private communication channel.

Include the following information when possible:

• A description of the vulnerability.
• The affected component or functionality.
• The conditions required to reproduce the issue.
• The potential impact.
• Any relevant version or environment information.

Please avoid including real credentials, personal information, or other sensitive data in your report.

The maintainer will review the report and determine whether it represents a security vulnerability.

Please understand that response times depend on availability, project activity, and the complexity of the issue.

Submitting a report does not guarantee that it will be accepted, that a fix will be produced, or that a release will be published by a particular date.

Please allow the maintainer reasonable time to investigate and address a confirmed vulnerability before publicly disclosing technical details.

If a vulnerability affects third-party software or services, avoid testing against systems you do not own or have explicit permission to assess.

Refer to the repository's documentation and release history to determine which versions are actively maintained.

Unless a repository specifies otherwise, no particular version or support period is guaranteed.