The earlier finding is confirmed: the package’s default CLI path can automatically run a newer release of itself from npm. The current self-update rule specifically classifies same-package npm updates with an off switch as suspicious, so this warrants a warning rather than a block.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Default CLI startup, unless ALEGRA_DATA_AGENT_NO_BOUNCE=1 is set or the command is help/version.
Impact
A newer publisher-controlled release can run without a separate update request. Under the current self-update rule, updating the same package from npm with an off switch warrants a warning, not a block.
Mechanism
Fetches the latest alegra-data-agent version from the npm registry and invokes it through pnpm dlx with the original arguments and inherited environment.
Evidence
index.mjsdist/main.jsdist/bounce.jsREADME.md
Network endpoints1
registry.npmjs.org/alegra-data-agent