@botbuddy/cli@1.63.39
BotBuddy — Swarm coordination CLI for multi-agent workflows
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe reviewed automatic network activity checks for this package’s update and delivers pending run results; relay credentials go to the package’s BotBuddy service. The flagged persistence behavior is behind explicit staging-pool commands, and no malicious behavior was established.
Decision evidence
public snapshot- The manifest defines CLI binaries and library exports, with no lifecycle scripts.
- The launcher runs pending delivery work during normal CLI invocations; help and inspection commands skip it.
- The update check contacts the npm registry for this package’s latest version and offers an update.
- Wait credentials are sent to the BotBuddy relay by default; the relay URL can be configured by the user.
- Staging-pool installation is a human-invoked command that checks its context before network or file operations.
- Runtime refresh accepts only tenant and pool identifiers and validates the existing pool before updating it.
- The package uses child processes, network access, and filesystem writes, including explicit staging-pool persistence.
- The shipped native daemon binaries could not be assessed from readable source in this review.
Source & flagged code
7 flaggedPackage source references child process execution.
src/update-check.mjsView on unpkg · L16Source writes installer persistence such as shell profile or service configuration.
Findings
Affected versions and remediation
This report applies to @botbuddy/cli@1.63.39.
See all versions of @botbuddy/cli for other recorded verdicts.
- Review the evidence and your use of @botbuddy/cli@1.63.39 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.