The reviewed risky capabilities serve BALDART’s CLI and framework functions and are gated by explicit commands, working-directory checks, or user confirmation. The package has no install hook that performs these actions automatically.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The CLI update check runs during eligible interactive CLI invocations; cleanup and setup actions run through their respective commands or user-confirmed configuration flows.
Impact
No unauthorized credential collection, unrelated data transfer, install-time persistence, or unrequested account action was identified.
Mechanism
The update check contacts the npm registry. Process cleanup is limited to orphaned MCP processes or a broker matching a specific working directory. Configuration installs require confirmation, and cron setup only creates a wrapper and prints instructions.
Evidence
~/.baldart/cli-update-check.jsonscripts/routines/<name>.sheslint.i18n.config.mjs.eslintrc.i18n.json
Network endpoints1
registry.npmjs.org/baldart/latest