@botbuddy/cli@1.63.29
BotBuddy — Swarm coordination CLI for multi-agent workflows
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe flagged process, network, credential, and persistence behaviors serve the CLI’s update, relay, and explicitly invoked staging-pool features. I found no install hook or automatic unrelated credential transfer.
Decision evidence
public snapshot- The manifest identifies a BotBuddy CLI and exposes its command binaries.
- The update check contacts the npm registry for this package’s latest version and caches the result for a warning.
- The wait command sends its bearer token to the configured BotBuddy relay, defaulting to api.bot-buddy.ai.
- Staging-pool installation is an explicit command guarded as human-only before network or file operations.
- The staging-pool command writes local configuration and installs a launchd job as part of that explicit installation.
- The manifest has no lifecycle scripts, so package installation does not automatically run these commands.
- The inspected network requests support the CLI’s update-check and BotBuddy relay functions; no unrelated credential recipient was identified.
- The launchd persistence behavior is part of an explicit staging-pool install command, not an install hook or automatic package startup.
Source & flagged code
7 flaggedPackage source references child process execution.
src/update-check.mjsView on unpkg · L15Source writes installer persistence such as shell profile or service configuration.
Findings
Affected versions and remediation
This report applies to @botbuddy/cli@1.63.29.
See all versions of @botbuddy/cli for other recorded verdicts.
- Review the evidence and your use of @botbuddy/cli@1.63.29 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.