Report suspected vulnerabilities privately through GitHub private vulnerability reporting. Repository administrators must enable that channel before public release. If it is unavailable, contact a repository maintainer privately; do not post credentials, private memory or an exploit containing confidential data publicly.
The latest released version is the target for fixes. Release candidates and research fixtures have only the validation scope recorded with them. Aimee owns authentication, authorization and scoped source publication; this runtime consumes the released projection. Information already delivered to a model host cannot be protected from that host by local grant checks or packaging.
Include the affected version or commit, runtime/model profile, reproduction steps and expected versus observed behavior. Use synthetic records and redact credentials. Model weights and production memory are unnecessary for most boundary reports.