The flagged source paths implement framework setup, migration, and process cleanup with user-triggered behavior or bounded safeguards. The CLI’s best-effort update check contacts only the npm registry for baldart’s latest version and does not send identifying package data.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The CLI update check runs during an interactive CLI invocation; project setup, migration, hooks, and scheduled wrappers are triggered by corresponding user commands.
Impact
No credential theft, unrelated data collection, hidden payload execution, or unrequested account action was found.
Mechanism
The update check fetches the baldart release version. Setup utilities write project configuration and wrappers; cron installation leaves the crontab edit to the user.
Evidence
~/.baldart/cli-update-check.json.claude/settings.jsonscripts/routines/<name>.shlefthook.yml.claude/skills/
Network endpoints1
registry.npmjs.org/baldart/latest