The launcher creates a meaningful but user-triggered remote binary execution risk because its download path lacks integrity verification. The package has no install lifecycle hook, and the inspected source does not establish a concrete attack, so this warrants a warning rather than a publish block.
Static reason
One or more suspicious static signals were detected.
Trigger
A user invokes apex when the binary is not already present.
Impact
A substituted or compromised release asset could execute with the invoking user's privileges.
Mechanism
The launcher downloads the platform-specific executable from a GitHub release and starts it with the user's arguments and environment, without a checksum or signature check in this path.
Network endpoints1
github.com/Apex-Foundation/copilot/releases/download/v${VERSION}/${assetName}