Until the first public beta is released, no public version is supported. After release, security fixes will target the newest available beta unless a release note states otherwise.
Do not report a suspected security vulnerability in a public issue.
Use GitHub's private vulnerability reporting feature for this repository when it is available so the report and follow-up remain confidential. Include the affected Reforge version, a clear description, reproduction steps or proof of concept when safe, and the potential impact.
If the private-reporting option is not visible, open a public issue titled Security contact request without technical details, logs, or attachments. A maintainer will arrange a private reporting channel.
Ordinary crashes, visual problems, workflow errors, and other non-security defects should use the public app bug form.
Do not include credentials, personal information, or secrets in either type of report.