The earlier review correctly identified a reachable default-path self-update, though the source stages releases in the cache rather than replacing the running executable immediately. The current rules specifically classify automatic updates of the same npm package with an off-switch as suspicious, so this is a warning rather than a remote-code-execution block.
Static reason
One or more suspicious static signals were detected.
Trigger
Ordinary CLI invocation, except plugin-hook invocations; update checks are throttled to roughly every 3–6 hours.
Impact
A later invocation can use the newer publisher release without the user explicitly running the update command. Under the current self-update rule this warrants a warning, not a publish block.
Mechanism
The CLI checks npm release metadata, fetches and verifies the matching package files, and can fetch a native archive from its project’s GitHub releases. It stages the update in the user cache for later use. OPENCRAWL_NO_UPDATE=1 disables automatic updates.
Evidence
runtime/opencrawl.jsREADME.md~/.cache/opencrawl/update.json~/.cache/opencrawl/releases/