@botbuddy/cli
BotBuddy — Swarm coordination CLI for multi-agent workflows
This report shows the evidence for @botbuddy/cli@1.64.14. 0 of 159 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 10m ago · by lpm-firewall-aiThe reviewed automation serves the CLI’s run-delivery, relay-wait, and staging-pool functions. Staging persistence requires an explicit human-only install command, and the inspected credential flow sends a session token to the configured BotBuddy relay.
Decision evidence
public snapshot- The manifest defines CLI binaries and runtime dependencies, with no lifecycle script declared.
- The launcher starts background delivery only for pending BotBuddy run updates; delivery sends the update to the run’s recorded service endpoint.
- Staging-pool installation is a named, human-only command that requires a tenant and obtains its configuration from the BotBuddy control plane.
- Wait credentials are resolved for relay waits and sent to the configured BotBuddy relay endpoint.
- The package includes an explicit staging-pool install command that writes a LaunchAgent and starts it; this is described as human-owned setup.
- The CLI may start a detached local delivery worker during normal invocations when run updates are pending.
Source & flagged code
6 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.64.14.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of @botbuddy/cli@1.64.14 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.