The latest release and the main branch receive security fixes. Earlier releases do not. The releases are listed on the GitHub Releases page.
Please do not open a public issue for a security problem.
Use GitHub private vulnerability reporting instead. Open the Security tab and choose Report a vulnerability, or go straight to the advisory form. Only the maintainers can see the report.
A good report includes the following.
- A description of the problem and its impact, for example script injection, data exposure or a leaked secret.
- Steps to reproduce it, or a proof of concept.
- The commit or the address of the deployment you tested.
- Relevant screenshots or logs with any secrets removed.
The report is triaged, fixed in private when it is valid, and released with a published advisory. Reporters who want credit are named once the fix has shipped. This project does not promise a reply time.
In scope are the code in this repository and its GitHub Actions workflows.
Out of scope are other people's deployments of this project, findings that need a compromised device or browser, and reports that only describe missing hardening without a way to exploit it.
Do not run automated scanning or load testing against a live deployment you do not own.