@botbuddy/cli@1.63.30
BotBuddy — Swarm coordination CLI for multi-agent workflows
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe flagged process execution and persistence paths are tied to explicit update or staging-pool operations, while the routine update check only fetches npm package metadata. Credential-bearing wait requests target the configured BotBuddy relay; no unrelated credential destination or malicious behavior was identified.
Decision evidence
public snapshot- The manifest describes a BotBuddy multi-agent workflow CLI and declares its command-line entry points; it has no lifecycle scripts.
- The update check performs a throttled lookup of npm’s latest package metadata and caches the result.
- Staging-pool installation is an explicit command that checks for a human session and requires tenant registration.
- Wait credentials are sent to the configured relay URL, which defaults to api.bot-buddy.ai.
Source & flagged code
6 flaggedPackage source references child process execution.
src/update-check.mjsView on unpkg · L15Source writes installer persistence such as shell profile or service configuration.
Findings
Affected versions and remediation
This report applies to @botbuddy/cli@1.63.30.
See all versions of @botbuddy/cli for other recorded verdicts.
- Review the evidence and your use of @botbuddy/cli@1.63.30 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.