Skip to content

Security: Haris16-code/KryonOS

SECURITY.md

Security Policy

Reporting a Security Vulnerability

If you discover a security vulnerability in KryonOS, please report it privately rather than opening a public GitHub issue.

Please include:

  • A clear description of the vulnerability
  • The affected component or feature
  • Steps to reproduce the issue
  • The potential impact
  • Any relevant logs, screenshots, or proof of concept

Private Reporting

Please use GitHub's private vulnerability reporting feature when available.

If private vulnerability reporting is not available, please contact the KryonOS maintainers privately before publicly disclosing the issue.

Security Updates

Security vulnerabilities will be investigated and addressed based on their severity and impact.

Once a fix is available, relevant security changes may be documented in the release notes or changelog.

Responsible Disclosure

Please allow the maintainers reasonable time to investigate and address a security vulnerability before publicly disclosing technical details.

We appreciate responsible security research and contributions that help make KryonOS safer and more secure.

There aren't any published security advisories