Skip to content

Security: masterai-top/TexasHoldem-Poker-Complete-Solution

Security

SECURITY.md

Security Policy

Reporting a vulnerability

Do not disclose security vulnerabilities, production credentials, private keys, real user data, or exploitable server details in a public GitHub issue.

Report security concerns privately by email:

Include the affected component, impact, reproduction steps, and a minimal proof of concept. Remove personal data, credentials, and unrelated confidential information before sending the report.

Response expectations

The project owner will review reproducible reports and determine remediation based on severity, affected versions, and the supported public scope. Acknowledgement or resolution times are not guaranteed.

Supported versions

Only the latest revision of the default branch is evaluated for public documentation and security fixes unless the project owner states otherwise.

Operational responsibility

Before production deployment, operators must conduct their own code review, dependency scanning, penetration testing, secret management, data-protection assessment, backup planning, and regional legal review. Never use demonstration credentials or sample configuration in production.

There aren't any published security advisories