@botbuddy/cli@1.64.5
BotBuddy — Swarm coordination CLI for multi-agent workflows
AI Security Review
scanned 15h ago · by lpm-firewall-aiThe reviewed network requests and credential use match the CLI's update and wait features, and persistence requires an explicit staging-pool install command. The native daemon binaries were unreadable, but their presence is consistent with the package's daemon feature and does not alone establish malicious behavior.
Decision evidence
public snapshot- The manifest describes a swarm coordination CLI and declares command entrypoints without lifecycle scripts.
- The update check fetches the package's latest version from registry.npmjs.org.
- Wait recovery sends its session token to the BotBuddy relay endpoint for the requested operation.
- Staging-pool installation is an explicit, human-gated command that writes and starts its job.
- The bundled native daemon binaries are unreadable in the available source views.
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.5.
See all versions of @botbuddy/cli for other recorded verdicts.
- Review the evidence and your use of @botbuddy/cli@1.64.5 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.