The package’s declared lifecycle script only syncs the version during prepublish. The flagged configuration, dependency installation, and cron behavior is confirmation-based or user-directed, and the runtime network check is a package-version lookup against npm.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The update check runs during an interactive CLI invocation; migration, i18n setup, and routine scheduling require user action.
Impact
The update check caches version information locally. No hostile data collection, hidden persistence, or unauthorized account action was identified.
Mechanism
The update check queries the baldart package version from the npm registry. Migration asks for confirmation, doctor requires confirmation to install gate dependencies, and cron scheduling is left to the user.
Evidence
~/.baldart/cli-update-check.json
Network endpoints1
registry.npmjs.org/baldart/latest