@botbuddy/cli@1.64.1
BotBuddy — Swarm coordination CLI for multi-agent workflows
AI Security Review
scanned 4d ago · by lpm-firewall-aiA user-run `bb wait` with malformed conditions automatically sends bounded diagnostics to the package’s relay using an existing credential. The event is minimized and does not expose secrets, but the runtime telemetry has no user-facing disclosure or opt-out, so this warrants a warning rather than a publish block.
Decision evidence
public snapshot- Invalid `bb wait` condition syntax triggers a setup-error report automatically.
- The report posts to `/sensor-ingest` on the configured relay and uses an existing bearer in the Authorization header.
- The event contains bounded error diagnostics; condition details are reduced to attempted types and parse-error categories, excluding raw condition text and values.
- The package manifest has no lifecycle scripts.
- The staging-pool LaunchAgent setup is behind an explicit `install` subcommand, which requires a tenant and checks that the caller is human.
- The telemetry is limited to diagnostic fields and does not include the bearer in the request body.
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.64.1.
See all versions of @botbuddy/cli for other recorded verdicts.
- Review the evidence and your use of @botbuddy/cli@1.64.1 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.