Skip to content

Security: StayElite/StayPresent

Security

SECURITY.md

Security Policy

Thank you for helping keep Stay Elite and our community secure.

We take security seriously and appreciate responsible disclosure of vulnerabilities.


Supported Versions

The following table indicates which versions currently receive security updates.

Version Supported
Latest Release
Development Branch
Older Releases

If you're using an unsupported version, please upgrade to the latest release before reporting security issues.


Reporting a Vulnerability

If you discover a security vulnerability, please do not open a public GitHub Issue.

Instead, report it privately by emailing:

📧 immortal.knight.king.0d@gmail.com

Please include the following information whenever possible:

  • A clear description of the vulnerability.
  • The affected repository and version.
  • Steps to reproduce the issue.
  • Proof of concept (if available).
  • Potential impact.
  • Suggested mitigation (optional).

Providing as much detail as possible helps us investigate and resolve the issue more quickly.


What to Expect

After receiving your report, we aim to:

  • Acknowledge your report within 48 hours.
  • Investigate the issue promptly.
  • Keep you informed about the progress.
  • Release a fix as soon as reasonably possible.
  • Publicly credit you for your responsible disclosure (if you wish).

Please note that response times may vary depending on the severity and complexity of the issue.


Coordinated Disclosure

We kindly ask that you:

  • Keep the vulnerability confidential until a fix has been released.
  • Avoid publicly disclosing exploit details before the issue is resolved.
  • Give our maintainers reasonable time to investigate and address the problem.

This helps protect users and the broader community.


Scope

This policy applies to all official Stay Elite repositories under the GitHub organization:

  • Source code
  • GitHub Actions workflows
  • Documentation
  • Websites
  • APIs
  • Packages and libraries

Third-party services and dependencies are outside the scope of this policy unless the issue directly affects a Stay Elite project.


Security Best Practices

When contributing, please:

  • Never commit secrets, API keys, or credentials.
  • Keep dependencies up to date.
  • Follow secure coding practices.
  • Validate user input.
  • Report security concerns responsibly.
  • Review code for potential vulnerabilities before submitting a Pull Request.

Thank You

We sincerely appreciate the efforts of security researchers and community members who help improve the security of Stay Elite.

Your responsible disclosure helps make our projects safer for everyone. ❤️

There aren't any published security advisories