The manifest has no install-time hook, and the routed CLI behaviors are consistent with the package’s framework purpose. The beacon can upload full session transcripts, but its skill explicitly describes that behavior and its reporting triggers.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
The CLI update check runs on eligible interactive invocations; transcript reporting occurs through the bat-beacon reporting flow, which the skill describes as available on explicit request or for detected framework malfunctions.
Impact
The reporting flow may share session content with the framework maintainer when activated. No malicious collection or install-time behavior was identified.
Mechanism
The notifier checks the npm registry. The beacon can collect a session transcript and upload it with a framework issue to the maintainer’s GitHub repository; this behavior is described in the skill.
Evidence
~/.baldart/cli-update-check.json.baldart/bat-beacon/outbox/sent/transcripts/