The earlier review’s behavior is present and reachable: ordinary CLI use can trigger a detached self-update, and the package uses registry.npmjs.org for version metadata. Under the current remote-code rule, an update of the same package from npm with the HYPERFRAMES_NO_AUTO_INSTALL=1 off-switch is suspicious, so this behavior does not require a publish block.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
An ordinary non-help CLI invocation, when cached update metadata indicates a newer compatible version and the install checks pass.
Impact
The package updates itself without a direct request for that update, changing the installed CLI version.
Mechanism
It starts a detached package-manager process to install hyperframes@<version> without an advance prompt. The install can be disabled with HYPERFRAMES_NO_AUTO_INSTALL=1; HYPERFRAMES_NO_UPDATE_CHECK=1 disables update checks.
Evidence
dist/cli.jsdist/autoUpdate-G7VXD2UI.jsdist/chunk-3NKJTDCV.js