Skip to content

Security: DeveloperPuneet/Rizzzler-Stable

SECURITY.md

Security Policy

Supported Versions

The latest version of Rizzzler is actively maintained and receives security updates.

Version Supported
Latest ✅ Yes
Older releases ❌ No

Reporting a Vulnerability

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

Instead, report it privately by contacting:

Please include:

  • A detailed description of the vulnerability
  • Steps to reproduce the issue
  • Proof of concept (if applicable)
  • Potential impact

What to Expect

After receiving your report, I will:

  • Acknowledge your report within 48 hours working hours
  • Investigate the issue
  • Work on a fix as quickly as possible
  • Keep you informed about the progress

If the report is valid, your contribution may be acknowledged in the project's release notes (unless you prefer to remain anonymous).


Scope

Examples of vulnerabilities include:

  • Authentication bypass
  • Authorization issues
  • Remote code execution
  • SQL/NoSQL injection
  • Cross-Site Scripting (XSS)
  • Cross-Site Request Forgery (CSRF)
  • Server-side request forgery (SSRF)
  • Sensitive data exposure
  • Dependency vulnerabilities
  • Other security-related issues

Disclosure Policy

Please allow reasonable time to investigate and resolve the issue before publicly disclosing it.

Responsible disclosure helps protect all users of Rizzzler.

Thank you for helping keep Rizzzler secure! ❤️

There aren't any published security advisories