@botbuddy/cli@1.64.3
BotBuddy — Swarm coordination CLI for multi-agent workflows
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe inspected behaviors match the package’s CLI purpose: wait credentials go to the configured BotBuddy relay, update checks retrieve package version metadata, and staging-pool persistence requires an explicit human-checked install command. No lifecycle scripts or unrelated credential flows were identified.
Decision evidence
public snapshot- The package manifest defines CLI entry points and no lifecycle scripts.
- The wait command resolves a BotBuddy agent session credential and sends it to the configured relay endpoint.
- The update check fetches only the package’s latest version from the npm registry.
- Staging-pool installation requires an explicit command and a human-only check before network or file operations.
- Run-delivery sends terminal updates using the session token sealed for the run’s owner.
- The package has a command that runs `npm install -g @botbuddy/cli@latest`.
- Explicit staging-pool installation writes configuration and a launchd plist, then registers the job.
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.3.
See all versions of @botbuddy/cli for other recorded verdicts.
- Review the evidence and your use of @botbuddy/cli@1.64.3 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.