The source establishes remote binary download and execution without integrity verification, while identifying a package-aligned repository and release version. This leaves a concrete, unresolved remote execution risk, but does not establish malicious behavior by the package.
Static reason
No blocking static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
Running the CLI when its home-directory binary is absent.
Impact
Execution depends on the contents served for the release asset; source inspection cannot establish the behavior of that binary.
Mechanism
The launcher downloads a release asset, writes it under the user's home directory, marks it executable where needed, and starts it with inherited arguments and environment.
Evidence
apex.cjspackage.json~/.apex/bin/apex
Network endpoints1
github.com/Apex-Accelerator/apexcli/releases/download/v1.5.80/apex-linux-x64