@botbuddy/cli@1.63.43
BotBuddy — Swarm coordination CLI for multi-agent workflows
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package’s network and persistence behavior is consistent with its CLI purpose: update checks query the npm registry, wait credentials go to the configured BotBuddy relay, and staging-pool persistence requires an explicit command. No install hook or concrete attack behavior was found.
Decision evidence
public snapshot- The manifest declares CLI binaries and runtime dependencies but no install lifecycle script.
- The update check contacts the npm registry for the latest package version and reads the response version.
- Wait requests use the configured relay URL, defaulting to the BotBuddy API, and send the wait token to that relay.
- Staging-pool persistence is part of an explicitly invoked command documented for human installation.
- The package’s network, process, and filesystem behavior fits its CLI, relay, update, and staging-pool functions.
- No credential flow to an unrelated host or other concrete attack behavior was identified.
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.43.
See all versions of @botbuddy/cli for other recorded verdicts.
- Review the evidence and your use of @botbuddy/cli@1.63.43 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.