@botbuddy/cli@1.63.3
⚠ Under reviewBotBuddy — Swarm coordination CLI for multi-agent workflows
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe inspected JavaScript did not establish a concrete attack, and the wait credential flow uses the BotBuddy relay by default. The shipped native daemon executables remain materially unresolved, so a clean verdict is not supported.
Decision evidence
public snapshot- The package includes a daemon directory, and its CLI source stages a daemon binary.
- Offline analysis could not identify the format or behavior of either shipped daemon executable, leaving their runtime unresolved.
- The inspected wait flow defaults to the BotBuddy relay, validates session tokens, and sends them with relay requests.
- The manifest declares no install lifecycle hook. The inspected JavaScript did not establish a concrete attack.
Source & flagged code
7 flaggedPackage source references child process execution.
src/update-check.mjsView on unpkg · L15Source writes installer persistence such as shell profile or service configuration.
Findings
Affected versions and remediation
This report applies to @botbuddy/cli@1.63.3.
See all versions of @botbuddy/cli for other recorded verdicts.
- Review the evidence and your use of @botbuddy/cli@1.63.3 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.