The earlier review correctly identified a reachable automatic self-update: the CLI checks npm and can install a newer HyperFrames release without a separate request. Under the current rules, a same-package npm self-update with an off-switch is suspicious and should be warned about, rather than blocked as remote code execution.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
On eligible CLI use, a background update check can cache a newer version; a subsequent eligible launch schedules the installation.
Impact
The installed CLI may be replaced by a newer release without a separate update request.
Mechanism
The CLI checks the HyperFrames channel at registry.npmjs.org and can launch a detached npm install of hyperframes at the newer version.
Evidence
dist/cli.jsdist/backgroundChecks-64YMYLKY.jsdist/backgroundChecksWorker.jsdist/chunk-TTK2RWRG.jsdist/autoUpdate-V5MR3BU5.jsGlobal npm-managed HyperFrames installationHyperFrames configuration and auto-update log under the directory resolved by hyperframesConfigDir()