The flagged behaviors are tied to the package's CLI and agent-framework functions: its update check queries the npm registry, and its overlay telemetry stays in a project-local file. The lifecycle script is prepublish-only, and the cron adapter leaves installation of the displayed crontab line to the user.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Running the CLI can start its update check; overlay logging runs when the registered Read hook is triggered. Cron setup is invoked by a user command.
Impact
No credential collection, unrelated outbound data transfer, or automatic crontab installation was identified in the reviewed paths.
Mechanism
The CLI checks the npm registry and caches the version. The overlay hook appends local usage metadata, while the cron adapter creates a wrapper and displays a crontab line for the user.
Evidence
~/.baldart/cli-update-check.json.baldart/telemetry/overlay-loads.jsonlscripts/routines/<name>.sh