The only process execution occurs after an explicit CLI invocation, and the missing binary is fetched from the same GitHub repository declared in the manifest. The dependency source excerpts show validation, parsing, and locale code, with no verified attack behavior.
Static reason
No blocking static signals were detected.
Trigger
The user runs the installed `apex` command and the expected binary is absent from the user’s Apex directory.
Impact
This runs the CLI binary supplied by the package’s release repository; the reviewed source does not establish credential theft or another attack.
Mechanism
The launcher downloads the platform binary over HTTPS from the declared repository’s versioned release path, then starts it with the user’s arguments and inherited environment.