It looks like you found something serious. Thank you. Please don't put it in a public issue; use the private route below.

Security policy¶

Security and privacy fixes are applied to the latest release.

Do not open a public issue for a vulnerability that could expose users, data, credentials, or systems. Use GitHub private vulnerability reporting when available. Otherwise email adam@matthewsteinberger.com with the subject Clippy Pet security report.

Include affected files or versions, reproduction steps, impact, and suggested mitigation. Expect acknowledgment within seven days and allow reasonable remediation time before disclosure. Use the public bug template for non-security defects.

Scope notes¶

Clippy Pet's attack surface is deliberately tiny: a manifest, an image, a POSIX shell installer, and CI. Things that would count as security issues here include the installer writing outside its documented locations, checksum or signature verification being bypassable, the release workflow being able to publish unsigned artifacts as signed, or a malicious spritesheetPath. Things that aren't: the ChatGPT desktop app or Codex CLI's own behaviour (report those to OpenAI), and Gatekeeper warnings on unsigned builds (documented on the macOS page).