pi-orchestrator-config@4.3.7
Orchestrator pattern for pi: specialist subagents, enforcement, code review loop, workflow commands
AI Security Review
scanned 15d ago · by lpm-firewall-aiThe source establishes a concrete, default-enabled exposure of agent conversations and prompt control to local network clients. The dashboard behavior is package-aligned, so the evidence supports a warning rather than a malicious verdict.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Starting an interactive TUI session while pidash is enabled by its default setting.
Impact
A device on the local network may be able to read session conversations and submit prompts to connected sessions.
Mechanism
The extension starts the daemon if needed, sends session history to it, and accepts browser WebSocket connections from permitted origins or requests without an Origin header.
AI rationale
The source establishes a concrete, default-enabled exposure of agent conversations and prompt control to local network clients. The dashboard behavior is package-aligned, so the evidence supports a warning rather than a malicious verdict.
Evidence
settings-keys.jsonextensions/pidash/pidash.tsscripts/pidash-server.tsscripts/daemon-shared.ts
Network endpoints2
0.0.0.0ws://127.0.0.1:${pidashPort}/ws/pi
Decision evidence
public snapshotAI called this Suspicious at 94.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- Pidash is enabled by default, and its TUI session handler connects automatically.
- When the daemon is absent, the extension starts it and sends session history over its WebSocket.
- The replay includes user messages and assistant text.
- The dashboard daemon listens on all interfaces and accepts private network origins.
- Browser WebSocket connections can watch sessions and send prompts; the upgrade path checks Origin but has no authentication gate.
Evidence against
- The data flow is part of the package's own dashboard feature, and the inspected source does not show transfer to an external collector.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsMinifiedPossibleObfuscationUrlStrings
Source & flagged code
7 flaggedextensions/image-gen/image-gen.tsView file
15import * as path from "node:path";
L16: import { execFileSync, spawn } from "node:child_process";
L17: import { fileURLToPath } from "node:url";
High
Child Process
Package source references child process execution.
extensions/image-gen/image-gen.tsView on unpkg · L15extensions/orchestrator/session-validation.tsView file
199" • macOS/Linux: curl -LsSf https://astral.sh/uv/install.sh | sh\n" +
L200: " • Windows: powershell -ExecutionPolicy ByPass -c \"irm https://astral.sh/uv/install.ps1 | iex\"\n" +
L201: " • Docs: https://docs.astral.sh/uv/",
High
Shell
Package source references shell execution.
extensions/orchestrator/session-validation.tsView on unpkg · L199extensions/shared/file-logger.ts
Findings
1 Critical4 High5 Medium4 Low
CriticalPrevious Version Dangerous Deltaextensions/pidash/pidash.ts
HighChild Processextensions/image-gen/image-gen.ts
HighShellextensions/orchestrator/session-validation.ts
HighRuntime Package Installscripts/serve-ui.ts
HighSemantic Analysis Limitedextensions/image-gen/image-gen.ts#virtual:normalized:round1
MediumDynamic Requireextensions/shared/file-logger.ts
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperscripts/build-extension-uis.sh
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to pi-orchestrator-config@4.3.7.
See all versions of pi-orchestrator-config for other recorded verdicts.
- Review the evidence and your use of pi-orchestrator-config@4.3.7 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.