@botbuddy/cli@1.64.6
BotBuddy — Swarm coordination CLI for multi-agent workflows
AI Security Review
scanned 14h ago · by lpm-firewall-aiThe manifest has no lifecycle scripts, and the flagged process execution and persistence support explicit CLI features. Credential use is directed to the BotBuddy relay, while the update check retrieves only the npm version.
Decision evidence
public snapshot- The manifest declares CLI entry points and no lifecycle scripts.
- The update check reads only the latest version from the npm registry.
- The wait flow sends its session token to the configured BotBuddy relay, defaulting to api.bot-buddy.ai.
- Telemetry code redacts credential-like values and removes raw output and environment fields.
- Staging-pool installation is an explicit command that checks for a human-run context before network or file operations.
- The package includes process execution and native daemon binaries.
- The staging-pool installer writes files and configures a launchd job, but this occurs through its explicit, human-gated install command.
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.6.
See all versions of @botbuddy/cli for other recorded verdicts.
- Review the evidence and your use of @botbuddy/cli@1.64.6 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.