The earlier review correctly identified a reachable, silent global self-update, but the current rules classify same-package npm self-updates with an off switch as suspicious, even when undisclosed. The postinstall download is the package binary from its declared repository's 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 `ocr` command, unless `OCR_NO_UPDATE` is set and unless the update check is still within its cooldown.
Impact
The global package installation can change without a prompt. Under the current self-update rule, this warrants a warning because the same-package npm update has an off switch.
Mechanism
A detached process checks the npm registry and runs `npm i -g` for this package when a newer version is available.
Evidence
package.jsonbin/ocr.jsscripts/update.jsscripts/install.js~/.opencodereview/last-update-check~/.opencodereview/update.lock~/.opencodereview/update-availablebin/opencodereviewglobal npm installation of @apdesign/open-code-review