The flagged behaviors are tied to CLI features: migration requests confirmation, cron setup prints instructions without editing the user's crontab, and dependency installation belongs to i18n gate setup. The startup update check contacts the npm registry for version information and does not auto-install updates.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
CLI startup may check the npm registry; configuration or maintenance commands trigger project changes and dependency installation.
Impact
Expected update-check traffic and project-local setup changes; no unauthorized credential collection, account action, or persistence was identified.
Mechanism
The updater requests package version information. Migration prompts before changing files, cron setup writes a wrapper and prints a crontab line, and i18n setup installs project lint dependencies.
Evidence
~/.baldart/cli-update-check.jsonscripts/routines/<name>.sh
Network endpoints1
registry.npmjs.org/baldart/latest