Security fixes are provided for the latest commit on main and the latest
pre-release, if one exists. Older commits, tags, and deployments are not
supported; reporters may be asked to reproduce a problem on a supported
version.
Do not open a public issue that contains credentials, cookies, private environment values, user media, titles, transcripts, generated articles, or other user content.
Use GitHub private vulnerability reporting when it is enabled for this repository. Otherwise, use a private maintainer contact channel exposed by the repository owner's GitHub profile or repository profile. This policy intentionally does not invent or publish an email address.
In the private report, include a concise impact description, supported-version reproduction steps, and the smallest redacted proof needed to understand the problem. Do not attach a real database, cookie export, environment file, provider credential, transcript, article archive, or user media. Coordinate before disclosing the issue publicly.