Skip to content

Latest commit

 

History

History
42 lines (28 loc) · 1.45 KB

SECURITY.md

File metadata and controls

42 lines (28 loc) · 1.45 KB

Security Policy

Supported Versions

We release patches for security vulnerabilities in the following versions:

  • Latest stable release
  • Previous stable release

Reporting a Vulnerability

If you discover a security vulnerability, please send an email to security@v4nt.com. Include the following details with your report:

  • Description of the vulnerability
  • Steps to reproduce the vulnerability
  • Potential impact of the vulnerability
  • Any possible mitigation you may have in mind

Security Updates

We take security seriously and will respond promptly to security issues. Once a vulnerability is reported, we will:

  1. Acknowledge receipt of the vulnerability report.
  2. Provide an estimated timeline for a fix.
  3. Keep you updated on the progress of the fix.
  4. Announce the fix once it is deployed.

Responsible Disclosure

We request that you do not publicly disclose the vulnerability until we have addressed it. This allows us to protect our users and provide a timely fix.

Security Best Practices

We recommend following these best practices to ensure the security of your own deployments:

  • Keep your software up-to-date with the latest security patches.
  • Use strong, unique passwords for all accounts.
  • Enable two-factor authentication where possible.
  • Regularly review and update your security configurations.

Contact

For any security-related issues, please contact us at security@v4nt.com.

Thank you for helping us keep OfficialV4NT/v4nt secure.