The inspected behavior matches a QC CLI client: it checks for updates during interactive use, while global installation requires an explicit command option. Credentials are sent as bearer tokens to the configured QC server, and no unrelated collection or default account action was found.
Static reason
One or more suspicious static signals were detected.
Trigger
The update notice runs during interactive CLI operations; package installation occurs only after the user runs update --apply.
Impact
No unauthorized data collection, credential forwarding, or account action was found. The update check and cache write are limited to version lookup and timestamp storage.
Mechanism
The notice fetches this package’s latest version from npm and caches a timestamp. The explicit updater installs this package from the npm registry. API requests send QC credentials to the configured QC server.
Evidence
~/.cache/intflow-qc/npm.json (fallback update-check cache; cache root can be configured)OS credential store (QC login credentials)
Network endpoints2
registry.npmjs.orgqc.intflow.dev (default; configurable QC server origin)