✨ Enhancement: Add SECURITY.md to define responsible vulnerability disclosure process

Is your feature request related to a problem? Please describe

This repository currently does not define a security disclosure policy or a SECURITY.md file.

As a result, contributors who discover security vulnerabilities do not have clear guidance on how to report them responsibly. This can lead to sensitive issues being opened as public GitHub issues instead of being privately disclosed to maintainers.

Describe the solution you'd like

Introduce a SECURITY.md file that clearly defines:

• How to report security vulnerabilities
• A private contact method for responsible disclosure
• Guidelines for handling and responding to such reports

This will help ensure security issues are handled appropriately and not exposed publicly before being fixed.

Describe alternatives you've considered

Without a SECURITY.md, contributors must rely on guesswork or open public issues for security concerns, which is not ideal for responsible disclosure.

Documenting this process in the repository is the standard and recommended approach for open-source projects.

Additional context

Many open-source projects include a SECURITY.md to guide contributors in reporting vulnerabilities responsibly. Adding one here will improve project governance and security practices.

Are you working on this?

Yes

Create SECURITY.md and review the issue requirements for vulnerability reporting, a private contact method, and response guidance. Confirm the disclosure process and contact details with maintainers before writing it. Done means the repository contains a clear policy that directs contributors away from public issue reports.