• launching Codex against a missing or substituted external drive
• silent recreation of a fresh internal ~/.codex state tree
• incomplete copies accepted without content/metadata checks
• SQLite copies accepted without integrity checks
• accidental deletion of the external state during rollback
• accidental modification of installed control files or the retained baseline
• concurrent state-changing commands

• a malicious process running as the same macOS user
• physical theft of an unencrypted SSD
• filesystem or hardware failure on the only active copy
• corruption caused by a hard disconnect during an active write
• application changes that stop honoring the documented location variables

Use encrypted APFS, maintain an independent backup, and review release changes before upgrading an active installation. Active installations pin their control-file hashes; do not replace package files behind a live manifest.

The package has no telemetry and makes no network requests after installation. Verification reports contain counts and cryptographic digests, not file names, xattr values, database rows, or file contents.

Open a GitHub security advisory or privately contact the repository owner. Do not publish a working destructive migration sequence before a fix is available.