The earlier review correctly identified a reachable, default self-update, and the architecture documentation inaccurately says none runs. The current rules specifically classify an update to the same package from npm as suspicious when it has an off switch; CAUSYNE_DISABLE_AUTOUPDATE provides that switch, so the update does not warrant a block.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Running the causyne CLI from an npm-managed installation; the check is enabled by default.
Impact
A newer package release can replace the installed CLI. The explicit self-update off switch makes this a warning under the current self-update rule, not a block.
Mechanism
It fetches the latest @causyne/agent version from the npm registry and uses npm to install that version globally with scripts disabled, then restarts.
Evidence
bin/causyne.jssrc/autoUpdate.jsdocs/ARCHITECTURE.mdsrc/autoUpdate.js update-state.json under the configured Causyne homeThe npm-managed global @causyne/agent installation