The earlier review correctly identified a reachable default self-update, but the current rules classify updating this same package from npm with an off-switch as suspicious, not block-worthy. The Slack and Granola credential sends are limited to explicit, documented connect commands, whose purpose is to send those credentials to the configured ITzNexus API.
Static reason
One or more suspicious static signals were detected.
Trigger
Running the CLI entry point, except when the check ran within the prior hour, dev mode is detected, or ITZNEXUS_SKIP_UPDATE is set.
Impact
The CLI can replace its global installation with the latest release without prior confirmation. Under the current remote-code rule, this same-package npm self-update with an off-switch is suspicious rather than a block.
Mechanism
Runs npm view and, if a different version is available, npm install -g @itznexus/itznexus-cli@latest, then re-executes the command.
Evidence
dist/index.jsdist/lib/auto-update.js~/.itznexus/last-update-checknpm-managed global installation of @itznexus/itznexus-cli
Network endpoints1
npm registry via npm CLI; host follows npm configuration