Skip to content

Latest commit

 

History

History
26 lines (18 loc) · 1.83 KB

SECURITY.md

File metadata and controls

26 lines (18 loc) · 1.83 KB

Security Policy

Supported Versions

Our commitment to security extends to the following version of the project:

Version Supported
@latest

Reporting a Vulnerability

We greatly value the security community's efforts in helping keep our project safe. If you've discovered a security vulnerability, your responsible disclosure is crucial for us. Here's how you can report it:

  1. Contact Method: Email us at blefnk@gmail.com.
  2. Email Subject: Please use a concise yet descriptive subject, such as "Security Vulnerability Found".
  3. Vulnerability Details: Provide a comprehensive description of the vulnerability. Include reproduction steps, and any other information that might help us understand and resolve the issue effectively.
  4. Proof of Concept: Attach any proof-of-concept or sample code if available. Please ensure that your research does not involve destructive testing or violate any laws.
  5. Encryption: For secure communication, use our public PGP key available on our website or public key servers.
  6. Response Timeline: We aim to acknowledge your report within [e.g., 48 hours] and will keep you updated on our progress.
  7. Investigation and Remediation: Our team will promptly investigate and work on resolving the issue. We'll maintain communication with you throughout this process.
  8. Disclosure Policy: Please refrain from public disclosure until we have mitigated the vulnerability. We will collaborate with you to decide on an appropriate disclosure timeline, considering the issue's severity.

We're grateful for your contributions to our project's security. Contributors who help improve our security may be publicly acknowledged (with consent).

Note: Our security policy may be updated periodically.