@botbuddy/cli@1.63.40
BotBuddy — Swarm coordination CLI for multi-agent workflows
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged process execution and persistence support documented CLI features, while staging-pool setup requires an explicit human-only command. Credential-bearing relay requests use the configured relay URL, and no concrete malicious behavior was found.
Decision evidence
public snapshot- The manifest describes a swarm-coordination CLI and exposes CLI binaries and optional reporter/telemetry exports.
- The update check queries npm for the latest version of this package.
- Staging-pool persistence runs through an explicit human-only install command that refuses agent sessions before network or file operations.
- Wait requests send the supplied session token to the configured relay URL.
- Run delivery handles pending terminal updates, and can be disabled with BOTBUDDY_RUN_DELIVERY=off; telemetry delivery targets BotBuddy’s service and filters event fields.
- No concrete credential theft, unrelated-target account action, destructive action, or concealed execution was identified.
- The reviewed network requests support package updates, configured relay operations, and BotBuddy run delivery.
- Staging-pool files and launch-agent setup require an explicit 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.63.40.
See all versions of @botbuddy/cli for other recorded verdicts.
- Review the evidence and your use of @botbuddy/cli@1.63.40 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.