The earlier review correctly identified a reachable, default-path self-update, but the current rules classify updates of this same package from npm as suspicious when an off switch exists; OCR_NO_UPDATE provides that switch. The GitHub URLs serve the project’s own install-time binary and checksum, so they do not independently require a block under the vendor-binary rule.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Running the `ocr` CLI when the update cooldown has elapsed; the check can be disabled with `OCR_NO_UPDATE`.
Impact
The global package may be replaced and its lifecycle scripts may run. Under the current self-update rule, this is warning-level because it updates this package from npm and has an off switch.
Mechanism
A detached updater requests the latest package version from the npm registry and runs `npm i -g @alibaba-group/open-code-review@<version>` if it is newer.
Evidence
bin/ocr.jsscripts/update.jspackage.jsonscripts/install.js~/.opencodereview/last-update-check~/.opencodereview/update.lock~/.opencodereview/update-available