The earlier review’s description is supported by the source: the default CLI path starts a detached updater, which checks npm and globally installs a newer release. The current self-update rule does not require blocking this behavior because the updater has the OCR_NO_UPDATE off switch; classify it as suspicious and warn.
Static reason
One or more suspicious static signals were detected.
Trigger
Running the documented `ocr` CLI, unless OCR_NO_UPDATE is set; the check is also subject to an 18-minute cooldown by default.
Impact
Can change the user’s global package installation without a separate update command. Under the current self-update rule, this warrants a warning because OCR_NO_UPDATE is an off switch; it does not warrant a block.
Mechanism
A detached updater checks the package’s latest version on the npm registry and runs `npm i -g @alibaba-group/open-code-review@<latest>` when it is newer than the installed binary.
Evidence
bin/ocr.jsscripts/update.js~/.opencodereview/last-update-check~/.opencodereview/update.lock~/.opencodereview/update-availableglobal npm installation of @alibaba-group/open-code-review