The previous review’s update chain is present and reachable: startup schedules the worker, which checks npm and can replace a global installation. The current self-update rule specifically makes this suspicious rather than malicious because it installs this same package from npm and provides off-switches; therefore the earlier undisclosed-update rationale does not require a block.
Static reason
One or more suspicious static signals were detected.
Trigger
CLI startup schedules a detached worker; it checks at most daily for eligible global npm installs.
Impact
The installed CLI can be replaced without a separate update command. Under the current rules, a self-update from npm for this same package with an off-switch is suspicious, not a publish block.
Mechanism
The worker fetches npm’s dist-tags for @oxygen-agent/cli, then invokes npm to install @oxygen-agent/cli@<latest>.
Evidence
dist/index.jsdist/auto-update.jsdist/cli-install.jsdist/commands/update.jsglobal npm installation of @oxygen-agent/cli
Network endpoints1
registry.npmjs.org/-/package/@oxygen-agent%2Fcli/dist-tags