@botbuddy/cli@1.63.35
BotBuddy — Swarm coordination CLI for multi-agent workflows
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe reviewed network and process behavior serves the CLI's coordination, wait, update, and Playwright functions. The flagged launchd persistence requires an explicit staging-pool install command, and the manifest contains no install lifecycle scripts.
Decision evidence
public snapshot- The manifest exposes CLI entry points and ends with dependency declarations; it has no lifecycle scripts.
- Wait requests send a session token to the BotBuddy relay or a relay URL supplied by the user.
- The launcher starts delivery only when command-run data exists, and delivery can be disabled with BOTBUDDY_RUN_DELIVERY=off.
- The staging-pool code is reached through an explicit CLI command and describes installation as a human action.
- The CLI uses child processes and network requests as part of its coordination and Playwright functions.
- The staging-pool command can install a launchd job and write pool configuration when explicitly invoked.
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.35.
See all versions of @botbuddy/cli for other recorded verdicts.
- Review the evidence and your use of @botbuddy/cli@1.63.35 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.