This repository accepts reports related to the safety of content published in this repository itself.

Examples include:

• accidental publication of sensitive details
• unsanitized identifiers, infrastructure references, or credentials
• dangerous procedural detail that exceeds the repository's publication boundary
• placeholder failures that reveal real data
• private or restricted material published by mistake

This repository is not a channel for:

• third-party vulnerability disclosure
• reporting vulnerabilities in targets, vendors, labs, or external services
• exploit requests
• takedown demands without repository-specific context

If your concern is not about content published in this repository, do not use this policy as a general security contact path.

Do not open a public issue containing sensitive details.

If possible, contact the maintainer through a private channel first. If no private route is available, open a minimal public issue without sensitive content and state that the repository may contain a publication-safety problem requiring maintainer review.

• affected file or path
• commit, branch, or page location
• why the content may be unsafe
• whether the risk is exposure, procedural detail, or failed sanitization
• suggested remediation, if known

Please allow reasonable time for review and remediation before discussing the issue publicly.