The earlier review correctly identified an automatic global self-update: it is reachable from the default CLI path, queries npm, and installs a newer version of this same package. Current rules classify self-updating from npm as suspicious when an off-switch exists (OCR_NO_UPDATE), so this behavior does not require a block; the postinstall GitHub request fetches the project's own binary and checksum, which is normal for this CLI.
Static reason
One or more suspicious static signals were detected.
Trigger
Running the `ocr` CLI when the update-check cooldown has elapsed; set `OCR_NO_UPDATE` to disable the updater.
Impact
The global CLI installation can change without a separate update command. The current rules treat this same-package npm self-update with an off-switch as suspicious, not as a publish block.
Mechanism
A detached process queries the package registry and runs `npm i -g @alibaba-group/open-code-review@<latest>` when that version is newer than the installed binary.
Evidence
bin/ocr.jsscripts/update.jspackage.jsonscripts/install.js~/.opencodereview/last-update-check~/.opencodereview/update.lock~/.opencodereview/update-available