Skip to content

Security: addonova/.github

Security

.github/SECURITY.md

Security Policy

We take the security of Addonova and the projects in this organization seriously. Thank you for helping keep our community and users safe.

Supported Versions

Security fixes are provided for the latest release of each actively maintained project. Projects that are archived, deprecated, or unmaintained are not supported unless stated otherwise in their repository.

Reporting a Vulnerability

Please do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.

Report vulnerabilities privately using GitHub's private vulnerability reporting:

  1. Open the Security tab of the affected repository.
  2. Select Report a vulnerability.
  3. Provide a detailed description, reproduction steps, affected versions, and any relevant proof of concept.

If private reporting is not enabled for a repository, contact the maintainers directly and ask for a secure channel before sharing details.

What to Include

  • A clear description of the issue and its potential impact.
  • Steps to reproduce, including a minimal proof of concept if possible.
  • Affected versions, platforms, and browsers.
  • Any suggested remediation or mitigations.
  • Whether you intend to disclose the issue publicly and, if so, your preferred timeline.

Our Commitment

  • We will acknowledge your report as soon as possible, typically within a few business days.
  • We will investigate and keep you informed of progress.
  • We will credit reporters in the advisory unless you prefer to remain anonymous.
  • We ask that you give us reasonable time to resolve the issue before public disclosure.

Safe Harbor

We consider security research conducted in good faith to be authorized and welcome. We will not pursue legal action against researchers who:

  • Make a good-faith effort to avoid privacy violations, data loss, and disruption of services.
  • Only interact with accounts and systems they own or have explicit permission to test.
  • Report findings privately and give us reasonable time to respond before disclosure.

Out of Scope

The following are generally out of scope:

  • Vulnerabilities in third-party dependencies that are already publicly known and patched.
  • Issues requiring physical access to a user's device.
  • Social engineering, spam, or denial-of-service attacks against project infrastructure.
  • Reports generated solely by automated scanners without evidence of a real, exploitable issue.

There aren't any published security advisories