@botbuddy/cli@1.64.11
BotBuddy — Swarm coordination CLI for multi-agent workflows
AI Security Review
scanned 4h ago · by lpm-firewall-aiThe flagged network, process, and persistence behavior is tied to the CLI’s relay, Playwright, update, and staging-pool features. No automatic install hook, unrelated credential transfer, or unrequested account action was found.
Decision evidence
public snapshot- The complete manifest defines CLI binaries and library entrypoints, with no lifecycle scripts.
- `bb wait` uses the BotBuddy relay by default (or an explicitly configured relay) and sends its session token to that relay’s event-stream endpoint.
- On wait setup errors, the package sends limited diagnostic fields to the relay’s sensor-ingest endpoint using the service bearer.
- The update check requests the latest package version from `registry.npmjs.org`.
- Staging-pool persistence is created by an explicit, human-only `install` command that requires a tenant.
- The source uses network access, environment variables, and child processes, but the inspected uses serve CLI, relay, Playwright, and update features.
- Native daemon binaries are present and their binary views are unsupported; the inspected source ties daemon setup to explicit CLI commands.
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.11.
See all versions of @botbuddy/cli for other recorded verdicts.
- Review the evidence and your use of @botbuddy/cli@1.64.11 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.