registry / @botbuddy/cli / 1.64.13
@botbuddy/cli@1.64.13
BotBuddy — Swarm coordination CLI for multi-agent workflows
AI Security Review
scanned 3h ago · by lpm-firewall-aiThe reviewed network requests and persistence serve the CLI’s relay, update-check, and staging-pool features. Staging installation is an explicit human command, and no malicious credential flow or unrelated automatic action was identified.
Static reason
No blocking static signals were detected.; previous stored version diff introduced dangerous source
Trigger
CLI commands; staging persistence requires the explicit staging-pool install command.
Impact
Observed network and persistence behavior serves the package's stated CLI and session-pool functions; no unrelated collection or attack behavior was found.
Mechanism
Wait commands use a session token with the configured BotBuddy relay. The update check fetches package version metadata from npm. The staging job maintains the installed session pool.
AI rationale
The reviewed network requests and persistence serve the CLI’s relay, update-check, and staging-pool features. Staging installation is an explicit human command, and no malicious credential flow or unrelated automatic action was identified.
Evidence
~/.botbuddy/update-check.json~/.botbuddy/staging-session-pool/~/Library/LaunchAgents/<registered-launchd-label>.plist
Network endpoints2
api.bot-buddy.airegistry.npmjs.org
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes CLI commands and two focused module exports; it declares no lifecycle scripts.
- Staging-pool installation checks for a human invocation before network or file operations, then registers the tenant pool and installs its job only through the explicit install command.
- The staging LaunchAgent runs the pool job at load after installation, which supports the documented session-pool feature.
- Wait requests send a per-session BotBuddy token to the configured BotBuddy relay as part of the wait feature.
- The stale-version check reads version metadata from the npm registry and caches the result locally.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
6 flaggedsrc/update-check.mjsView file
16import { readFileSync } from "node:fs";
L17: import { spawn, spawnSync } from "node:child_process";
L18: import { homedir } from "node:os";
High
Child Process
Package source references child process execution.
src/update-check.mjsView on unpkg · L16src/staging-pool/refresh-runtime.mjsView file
26const jobPath = join(app, "job.mjs");
L27: async function owned(path, directory = false, privateFile = false) {
L28: const info = await fs.lstat(path);
...
L42: const before = await configBytes();
L43: const installed = validateInstalledConfig(JSON.parse(before));
L44: const previous = installed.poolBinding;
...
L61: const rows = await fetchRegisteredPools({
L62: exec: (file, args, callOptions) => exec(process.execPath, [file, ...args], callOptions),
L63: botbuddyBin: cliEntry, env, tenant, poolId, preserveAgentContext: true, requireTenantMatch: true,
...
L125: await fs.rename(configTemp, configPath);
L126: return { ok: true, command: "refresh-runtime", tenant, poolId, runtimeVersion: metadata.version, runtimeSha256: contentDigest, personaAliases: Object.keys(next.personas), producer:
Medium
Install Persistence
Source writes installer persistence such as shell profile or service configuration.
Findings
4 High5 Medium3 Low
HighChild Processsrc/update-check.mjs
HighSame File Env Network Executionsrc/pw/daemon.mjs
HighTrigger Reachable Persistencesrc/staging-pool/cli.mjs
HighPrevious Version Dangerous Deltasrc/commands.mjs
MediumNetwork
MediumEnvironment Vars
MediumInstall Persistencesrc/staging-pool/refresh-runtime.mjs
MediumShips Native Binarydaemon/bin/darwin-arm64/botbuddy-daemon
MediumStructural Risk Force Deep Review
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @botbuddy/cli@1.64.13.
See all versions of @botbuddy/cli for other recorded verdicts.
- Review the evidence and your use of @botbuddy/cli@1.64.13 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.