The CLI performs an automatic npm self-update on its default startup path, with CAUSYNE_DISABLE_AUTOUPDATE as an off-switch. Under the current self-update rule this is suspicious and should be warned on, not blocked; the cited provider-key route targets the matching provider endpoint.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Starting the CLI from a managed npm or Causyne installer installation, unless CAUSYNE_DISABLE_AUTOUPDATE is set to 1 or true.
Impact
New vendor-published code can replace and run over the installed version without a separate update command.
Mechanism
The CLI checks the package's npm registry metadata and uses npm to globally install a newer @causyne/agent release, then restarts.
Evidence
bin/causyne.jssrc/autoUpdate.jssrc/dynamicCatalogue.js
Network endpoints2
registry.npmjs.orgapi.anthropic.com