@botbuddy/cli@1.63.38
BotBuddy — Swarm coordination CLI for multi-agent workflows
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe manifest has no install hooks, and the flagged process, network, and persistence behavior is tied to the CLI’s documented command flows. The native daemon binaries were not readable in the provided views, but their presence alone does not establish malicious behavior.
Decision evidence
public snapshot- The manifest exposes CLI entry points and has no lifecycle scripts.
- The launcher starts run-delivery for terminal updates; its source says delivery uses the session token sealed for that run’s owner.
- Wait requests use the BotBuddy relay by default and require a session token before posting.
- Staging-pool installation is an explicit command requiring a tenant and checks that the caller is human before network or file operations.
- The package ships native daemon binaries whose behavior could not be established from the available binary views.
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.38.
See all versions of @botbuddy/cli for other recorded verdicts.
- Review the evidence and your use of @botbuddy/cli@1.63.38 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.