The earlier review’s update behavior is accurate and reachable, but the current rules classify an npm self-update of the same package with an off-switch as suspicious rather than blockable. The credential commands require explicit connect actions and send their supplied values through the configured API client to the package’s service.
Static reason
One or more suspicious static signals were detected.
Trigger
Normal CLI invocation, after the one-hour update-check interval; skipped in development mode or when ITZNEXUS_SKIP_UPDATE is set.
Impact
New package code can replace the global installation and execute as part of the command. Under the current self-update rule, this warrants a warning because an environment-variable off-switch exists.
Mechanism
Runs npm view and npm install -g for @itznexus/itznexus-cli@latest, then starts a fresh process with the original arguments.
Evidence
dist/index.jsdist/lib/auto-update.jsdist/lib/api.jsdist/lib/config.jsdist/commands/api/slack-accounts.js~/.itznexus/last-update-checknpm-managed global installation of @itznexus/itznexus-cli