@botbuddy/cli@1.63.37
BotBuddy — Swarm coordination CLI for multi-agent workflows
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged process, network, credential, and persistence behavior has contextual, user-facing purposes. The package has no lifecycle script, relay credentials are used for relay requests, and staging-pool persistence is initiated through an explicit human-gated command.
Decision evidence
public snapshot- The manifest exposes CLI binaries and library exports and declares no lifecycle script.
- The update check fetches package version metadata from registry.npmjs.org; it does not include host or project data in that request.
- Relay waits validate the session-token format and send the token to the configured relay endpoint; the default is the BotBuddy relay.
- Staging-pool installation is an explicit command gated as human-only and requires a tenant.
- Runtime refresh accepts only tenant and pool identifiers and validates the existing pool before updating it.
- When invoked, staging-pool install writes a LaunchAgent configuration and starts the job.
- Most CLI commands perform a version check against the npm registry; wait, telemetry, usage, test-ingest, and JSON invocations are excluded.
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.37.
See all versions of @botbuddy/cli for other recorded verdicts.
- Review the evidence and your use of @botbuddy/cli@1.63.37 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.