The earlier review correctly identified a default-path self-update, but the current rules classify updating this same package from npm with an off-switch as suspicious, not a publish block. The postinstall binary download is from the package’s own GitHub release host and is checksum-verified, so it does not independently require a block.
Static reason
One or more suspicious static signals were detected.
Trigger
Running the CLI when its update-check cooldown has elapsed; OCR_NO_UPDATE disables this path.
Impact
The global package may be replaced without a separate update request, changing the CLI version used by the user.
Mechanism
A detached updater compares the installed binary version with the latest version from registry.npmjs.org and runs npm install -g for this package when newer.
Evidence
bin/ocr.jsscripts/update.jsscripts/install.jspackage.json~/.opencodereview/last-update-check~/.opencodereview/update.lock~/.opencodereview/update-availableglobal installation of @itechmeat/open-code-review