The executable download and launch create a meaningful remote payload risk, and the mismatch between the manifest repository and runtime source is unresolved. Because activation requires a user to invoke the CLI and no malicious payload behavior is established, this warrants a warning rather than a block.
Static reason
One or more suspicious static signals were detected.
Trigger
User invokes the apex command when its cached binary is missing.
Impact
The downloaded binary receives the user's execution context. The different repository named in the manifest leaves the intended release source unresolved.
Mechanism
The launcher downloads a release asset from GitHub, marks it executable, and starts it with the caller's arguments and environment; this runtime path has no integrity check.
Network endpoints1
github.com/Apex-Foundation/copilot/releases/download/v${VERSION}/${assetName}