The earlier review correctly identified a reachable automatic self-update, but built-in help documents both the automatic upgrade and FMIX_NO_AUTO_UPGRADE as its opt-out. Under the current self-update rule, that disclosure makes this a warning; the separate POST finding is an explicitly installed hook using a configured endpoint, not command-output exfiltration to a fixed host.
Static reason
One or more suspicious static signals were detected.
Trigger
Starting an eligible, non-read-only command using an installed runtime, unless FMIX_NO_AUTO_UPGRADE=1 or another skip condition applies.
Impact
The runner can change without a separate update command. Built-in help documents the opt-out, so the current self-update rule calls for a warning rather than a block.
Mechanism
A detached check queries the latest release, downloads the matching runner assets from the project’s GitHub releases, verifies them, and installs the runner for a later invocation.
Evidence
bin/fmix${FMIX_HOME:-${HOME:-}/.ct-fmix}/auto-upgrade.stamp${FMIX_INSTALL_DIR:-${HOME:-}/.local/bin}/fmix${TMPDIR:-/tmp}/fmix-auto-upgrade.XXXXXX