The package performs automatic self-updates on default startup, and the documented opt-out does not make that behavior a user-requested update. The source identifies the update as the CLI’s own release flow, so this is a warning-level self-update risk rather than evidence of a malicious payload.
Static reason
One or more suspicious static signals were detected.
Trigger
Default CLI startup for ordinary commands, with checks due every 3–6 hours; OPENCRAWL_NO_UPDATE=1 disables them.
Impact
A newly published release can replace the CLI and run on a later invocation without a separate update command.
Mechanism
The runtime checks the latest CLI release on the npm registry and stages a newer version in its cache. Managed installations use the project’s GitHub release channel.
Evidence
runtime/opencrawl.jsbin/opencrawl.cjspackage.json$XDG_CACHE_HOME/opencrawl/update.json$XDG_CACHE_HOME/opencrawl/releases/<version>$XDG_DATA_HOME/opencrawl/versions/<version>
Network endpoints3
registry.npmjs.org/@getopencrawl%2fcli/latest