The manifest has no install hook; its only lifecycle script syncs the package version. The flagged process cleanup, migration, routine setup, dependency installation, and report sending are scoped to explicit commands or user follow-up, with no attack behavior identified.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
CLI commands or framework skills invoked by the user; the update check runs from the CLI in eligible interactive sessions.
Impact
No unrequested credential collection, account actions, install-time data transfer, or unrelated persistence was found in the inspected paths.
Mechanism
Migration prompts before writing, cron setup creates a wrapper and leaves crontab editing to the user, and batbeacon requires an explicit send command. The update check queries the package’s npm registry entry.
Evidence
~/.baldart/cli-update-check.jsonscripts/routines/<name>.sh.baldart/batbeacon/outbox/.baldart/batbeacon/sent/
Network endpoints2
registry.npmjs.org/baldart/latest