@botbuddy/cli@1.63.42
BotBuddy — Swarm coordination CLI for multi-agent workflows
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged process execution and persistence are tied to explicit CLI operations, and the reviewed credential flow sends tokens to the configured BotBuddy relay. Automatic update checks fetch only package version metadata from npm.
Decision evidence
public snapshot- The manifest exposes CLI binaries and subpath exports for its reporter and telemetry modules.
- Update checks request only the package’s latest version from the npm registry.
- The staging-pool launch-agent setup is behind an explicit install command and checks that the caller is human-operated before network or file activity.
- Wait requests send their token to the configured relay URL, which defaults to BotBuddy’s API.
- The reviewed source shows no malicious credential transfer or unrelated collector.
- The flagged persistence supports the package’s staging-session-pool feature and is installed through an explicit command.
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.42.
See all versions of @botbuddy/cli for other recorded verdicts.
- Review the evidence and your use of @botbuddy/cli@1.63.42 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.