The CLI automatically updates itself from the npm registry on eligible invocations, with OPENCRAWL_NO_UPDATE=1 as an off switch. The package’s update rule makes this a warning-level capability, not evidence of malicious behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
Ordinary eligible CLI commands schedule an update check; checks recur every 3–6 hours.
Impact
A newer package release may run on later invocations without a separate update command; this is a warning-level self-update capability.
Mechanism
The launcher checks the latest @getopencrawl/cli release and installs a newer version into a per-user cache, where later invocations can select it. OPENCRAWL_NO_UPDATE=1 disables automatic updates.
Evidence
runtime/opencrawl.jsbin/opencrawl.cjs~/.cache/opencrawl/update.json~/.cache/opencrawl/releases/<version>/$XDG_CACHE_HOME/opencrawl/update.json$XDG_CACHE_HOME/opencrawl/releases/<version>/