The cited entrypoint makes the updater reachable after CLI commands, and the updater does query npm and globally install this same package when a newer version exists; its state writes only record the check and claim. The current self-update rule treats same-package npm updates with an off-switch as suspicious, so the earlier rationale does not require a block under the current rules.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Runs on CLI process exit after the normal command path; the update worker runs the check.
Impact
A later release can replace the installed CLI without a separate update request. Under the current self-update rule, this is a warning-level capability because it updates the same package from npm and has an off-switch.
Mechanism
Unless NETA_CLI_AUTO_UPDATE=0, it checks the npm registry for this package’s latest or dev version and globally installs it when newer.
Evidence
package.jsondist/index.cjs~/.cache/neta-cli/self-update.json~/.cache/neta-cli/self-update.lock/tmp/neta-cli-install.lockThe global @neta-art/neta-cli installation, via npm