Only the latest release and the main branch are actively supported with security updates.
Please do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.
Report vulnerabilities privately using GitHub Private Vulnerability Reporting:
- Go to the repository's Security tab.
- Click Report a vulnerability (under Advisories).
- Provide a clear description, reproduction steps, affected versions/files, and potential impact.
Reports involving vulnerabilities in upstream or third-party dependencies are welcome—especially if upstream maintainers have ignored or stalled on a fix. If a safe workaround, mitigation, or isolation pattern can be implemented in this project to keep affected workflows usable, I am interested in evaluating and shipping it.
This project is maintained independently by a solo developer on a best-effort basis:
- Acknowledgment: Within 7 days of report submission.
- Triage & Fix: Severity-dependent; critical issues are prioritized.
- Coordinated Disclosure: Please allow reasonable time to investigate and release a fix or mitigation before public disclosure. Credit will be given in the GitHub Security Advisory unless you prefer to remain anonymous.
- Denial-of-service, spam, or social engineering targeting GitHub infrastructure.
- Issues requiring pre-existing local root/admin privileges or physical access unless explicitly part of the project's threat model.