Skip to content

Files

Latest commit

f5f06c3 · Oct 25, 2024

History

History
34 lines (21 loc) · 1.44 KB

SECURITY.md

File metadata and controls

34 lines (21 loc) · 1.44 KB

Security

We take the security of our software seriously. If you discover a security vulnerability in this project, please follow the instructions below to report it responsibly.

Reporting Security Issues

Do not report vulnerabilities through public issue trackers.

Instead, please report them via email to:
your-email@example.com

To protect sensitive information, consider encrypting your message using PGP if applicable.

Information to Include in Your Report

Providing the following details (where applicable) will help us assess the issue more effectively:

  • Type of issue (e.g., buffer overflow, SQL injection, cross-site scripting, etc.)
  • Affected file paths or components
  • Location of the issue (branch/commit/tag or direct URL)
  • Configuration details required to reproduce the issue
  • Step-by-step instructions to reproduce the vulnerability
  • Proof-of-concept or exploit code (if available)
  • Impact assessment, including how an attacker could exploit the issue

We appreciate your effort in identifying security issues. Thank you for helping us maintain the safety and reliability of this project!

Response Time

We aim to respond to vulnerability reports within 24 hours. If you don’t receive a response, feel free to follow up to ensure your message was received.

Preferred Language

We prefer all communication in English.