Skip to content

Security: shrey2597/CricScope

Security

SECURITY.md

πŸ” Security Policy

Supported Versions

The main branch is actively maintained with security updates and bug fixes.

If you are using an older version or a personal fork, we strongly recommend syncing regularly with the latest upstream repository updates.


🚨 Reporting a Vulnerability

We take security issues seriously and appreciate responsible disclosure from the community.

Please do NOT report security vulnerabilities publicly through GitHub Issues.


πŸ“© How to Report

If you discover a vulnerability:

  1. Report the issue privately to the project maintainer
  2. Include detailed reproduction steps
  3. Explain the potential impact
  4. Include screenshots or proof-of-concept if applicable

⏱ Response Timeline

  • Initial acknowledgment within 48 hours
  • Verification and investigation process
  • Security fix implementation
  • Responsible disclosure coordination
  • Resolution notification after patch deployment

🀝 Responsible Disclosure

Please avoid publicly sharing vulnerabilities until a fix has been released.

Responsible disclosure helps keep the project and community secure.


❀️ Thank You

Thank you for helping improve the security and reliability of CricScope.

There aren't any published security advisories