Please help protect Traverse users by keeping vulnerability details out of public issues, discussions and community channels. Never attach private files, keys, tokens, passwords or unreviewed crash captures.
If the repository's Security → Report a vulnerability action is available, use it for a private report. If it is unavailable, ask a maintainer in the Respawn Studios community for a private reporting contact without posting the vulnerability or private evidence in the channel. This is a contact route, not permission to share secrets with an unverified user.
A useful private report includes the app version/build, macOS version, the affected feature, expected and observed behavior, and a small reproduction using disposable data. Describe the potential impact and which access was required. Keep real credentials and personal documents out of the reproduction. Coordinate public disclosure with maintainers after the report is understood.
The newest published release is the maintenance target. Prerelease builds are reviewed on a best-effort basis; older betas may require reproduction on a current candidate. This policy promises no fixed response time or bug-bounty payment.
Use Issues for non-sensitive bugs. Traverse's local report window lets you review, redact, edit and export diagnostics before sharing. Its privacy helper cannot guarantee that arbitrary comments or attachments contain no private information. GitHub attachments upload when attached, before an issue is submitted. See Privacy.