The CLI checks for updates to @prestyj/cli and can install that package globally in the background during ordinary startup when an update is pending. This is recognizable updater code, but silently modifying a separate global package without confirmation is a meaningful risk, so warn rather than block as malicious.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user starts the orchestrator after a prior registry check recorded a newer version.
Impact
The global @prestyj/cli installation can be replaced and its new code run without the user explicitly choosing to update it. The updater behavior is clear, but the package identity mismatch and lack of confirmation create a real risk.
Mechanism
The CLI checks saved update state and launches a detached package-manager command to install @prestyj/cli@latest globally.
Evidence
dist/cli.jsdist/chunk-EWD6HKWJ.js~/.ezcoder/update-state.json
Network endpoints1
registry.npmjs.org/@prestyj/cli/latest