@botbuddy/cli@1.64.0
BotBuddy — Swarm coordination CLI for multi-agent workflows
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe manifest has no lifecycle scripts, and the flagged network, process and persistence behavior is consistent with this coordination CLI’s purpose. Credential-bearing relay calls use a per-session token for BotBuddy, while setup actions require explicit commands.
Decision evidence
public snapshot- The manifest exposes CLI binaries and package-specific reporter and telemetry modules.
- Wait requests use the per-session BotBuddy token for relay registration; the code says the command fails closed without it.
- Staging pool installation is a named human-only operation that requires a tenant.
- Daemon updater installation runs only through the explicit `bb daemon updater-install` command.
- The update check is described as a throttled npm version check; updating is a separate `botbuddy update` command.
- The launcher’s delivery process handles pending terminal updates from `bb run` and is skipped for help and inspection.
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.0.
See all versions of @botbuddy/cli for other recorded verdicts.
- Review the evidence and your use of @botbuddy/cli@1.64.0 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.