The flagged behaviors have package-related explanations: CLI updates use npm with install scripts disabled, and API credentials go to the configured service. No lifecycle hook or unrelated credential flow was found in the reviewed paths.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The CLI runs when invoked; automatic upgrade is attempted only after an API upgrade-required response, and the update check uses a separate internal command.
Impact
No unauthorized data collection, account action, or unrelated code execution was found in the reviewed paths.
Mechanism
The CLI sends its configured token to its configured API base URL. Its updater installs the CLI globally with npm while disabling install scripts; the update check fetches registry version metadata.
Network endpoints2
harness.infra.oneregistry.npmjs.org