Security fixes are provided for the latest stable LumeTrace release.
| Version | Supported |
|---|---|
| Latest stable release | Yes |
| Older releases | No |
develop and other development builds |
No |
Before reporting a vulnerability, confirm that it is reproducible with the latest stable release.
Do not open a public GitHub issue for a vulnerability that could put users, files, credentials, or devices at risk.
Submit the report privately through GitHub Private Vulnerability Reporting. If that form is unavailable, contact the maintainer through the LumeTrace Discord community and request a private reporting channel. Do not post vulnerability details in a public Discord channel.
Include:
- the affected LumeTrace version and macOS version;
- a clear description of the vulnerability and its impact;
- the minimum steps needed to reproduce it;
- a proof of concept, screenshots, or logs when safe to share;
- any known workaround or mitigation.
Remove API keys, passwords, private file contents, personal information, and other secrets before sending a report.
We aim to acknowledge complete reports within five business days. Fix and disclosure timing depends on severity, reproducibility, and release risk. Please allow time for investigation and a coordinated release before publishing details.
For ordinary bugs and feature requests that do not create a security risk, use GitHub Issues.