Do not open a public issue, pull request, discussion, or repository comment for a potential security vulnerability. This repository is intentionally small, but examples, scripts, links, and future integrations can still create risk.

Use GitHub’s private security-advisory reporting flow for this repository. Include the affected path, a concise description, safe reproduction steps, impact, and any proposed mitigation. Do not include credentials, personal data, production URLs containing private query data, or destructive proof-of-concept payloads.

Report vulnerabilities in repository code, automated workflows, published examples, documentation that creates material misuse risk, and repository configuration. General product support, feature requests, or conceptual disagreements belong in issues or discussions and should not contain sensitive details.

Maintainers will acknowledge a report, assess its severity and scope, coordinate remediation privately where appropriate, and publish a concise advisory or changelog only after the affected users can safely act. No contributor should exploit, publicly disclose, or attempt to access data through a suspected weakness.