@botbuddy/cli@1.63.44
BotBuddy — Swarm coordination CLI for multi-agent workflows
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe reviewed network and credential flows serve the package’s update and BotBuddy relay functions. Persistence is behind an explicit human-only install command, and the manifest declares no lifecycle scripts.
Decision evidence
public snapshot- The manifest exposes CLI commands and two explicit library exports, with no lifecycle scripts declared.
- The updater checks only the package’s latest version at the npm registry and caches the result.
- The updater runs through the command dispatcher; it is not an install hook.
- Staging-pool installation is an explicit command guarded as human-only before network or file operations.
- Wait requests use the BotBuddy relay by default and send the supplied agent token to its event-stream endpoint.
- Run-delivery retries terminal updates for prior runs and starts on demand when the CLI is invoked.
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.44.
See all versions of @botbuddy/cli for other recorded verdicts.
- Review the evidence and your use of @botbuddy/cli@1.63.44 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.