Skip to content

Security: OwenOrcan/YiraBot-Crawler

Security

SECURITY.md

Security Policy for YiraBot

Introduction

At YiraBot, we take the security of our software and the trust of our users seriously. The purpose of this policy is to provide guidelines on reporting security vulnerabilities and to describe how we address these concerns.

Supported Versions

Security updates and patches will be applied only to the most recent version of YiraBot. The following table outlines which versions are currently receiving security updates:

Version Supported
> 1.0.7
< 1.0.7

Reporting a Vulnerability

If you believe you have found a security vulnerability in YiraBot, please follow these steps:

  1. Do Not Publish the Vulnerability Publicly:

    • Please do not report security vulnerabilities through public GitHub issues, forums, or other public channels.
  2. Send a Detailed Report:

    • Email your security findings to Owen Orcan
    • Include detailed information about the issue, steps to reproduce, and any other information that might be helpful for understanding and resolving the vulnerability.
  3. Wait for Response:

    • After submitting your report, please give us a reasonable amount of time to respond and address the issue before disclosing it to others.
  4. Disclosure Handling:

    • Once the vulnerability has been evaluated and addressed, we may discuss it publicly to inform our user base. We will coordinate any public announcement with you to ensure that accurate information is released.

Security Update Process

Upon receiving a report of a security vulnerability, our team will follow this process:

  1. Confirmation and Evaluation:

    • Confirm the issue and assess its impact and severity.
  2. Fixing the Issue:

    • Develop a security patch or workaround to address the vulnerability.
  3. Releasing an Update:

    • Release an updated version of YiraBot that resolves the issue.
  4. Notifying Users:

    • Inform users about the vulnerability and encourage them to update to the latest version.
  5. Post-release Analysis:

    • Conduct a post-incident review to learn from the vulnerability and improve future security practices.

Commitment

We are committed to ensuring the security and privacy of our users. We appreciate your help in keeping YiraBot safe and secure.

Thank you for supporting YiraBot and its security.

There aren’t any published security advisories