Skip to content

Latest commit

 

History

History
43 lines (29 loc) · 1.93 KB

SECURITY.md

File metadata and controls

43 lines (29 loc) · 1.93 KB

Security Policy

Supported Versions

We release patches for security vulnerabilities in the following versions:

Version Supported
1.x

Reporting a Vulnerability

If you discover a security vulnerability within this project, please follow these steps to report it:

  1. Do not open a public issue.
  2. Send an email to [email protected] with the details of the vulnerability.
  3. Please include the following in your email:
    • A description of the vulnerability.
    • Steps to reproduce the issue.
    • Any potential impacts and your assessment of the severity.
    • Any possible mitigations or workarounds.

We will review your report and respond within 5 business days with an acknowledgment of the issue. We aim to address all security vulnerabilities in a timely manner and will work with you to understand the scope and impact of the reported issue.

Handling Vulnerabilities

  • Once a vulnerability is reported, we will verify the issue and determine the scope and impact.
  • We will work on a fix and perform internal testing to ensure the issue is resolved.
  • A security advisory will be published, and we will notify affected users and developers about the vulnerability and the fix.
  • The patched version will be released, and we will update the repository with the necessary changes.

Security Best Practices

While using TickWatch, we recommend the following security best practices:

  • Always keep your dependencies up to date to ensure you have the latest security patches.
  • Regularly audit your project's dependencies for known vulnerabilities.
  • Avoid using the plugin in an environment where untrusted users can input data directly.
  • Follow secure coding practices and validate all inputs when integrating with other components or plugins.

Contact

If you have any questions or need further assistance, please reach out to us at [email protected].