pi-orchestrator-config@4.16.0
Orchestrator pattern for pi: specialist subagents, enforcement, code review loop, workflow commands
AI Security Review
scanned 15d ago · by lpm-firewall-aiThe source supports a real runtime exposure: default-enabled pidash streams session history to a daemon reachable on the LAN, where browser clients can watch sessions and issue supported commands without authentication in the inspected path. This is a warning for dangerous dashboard capability, not evidence of malicious install behavior or third-party exfiltration.
Decision evidence
public snapshot- The manifest defines only a UI build and a prepack hook; it has no install lifecycle hook.
- Pidash is enabled by default and hooks session startup to connect automatically.
- Pidash sends session history and user messages to its daemon over a WebSocket.
- The daemon listens on all interfaces and exposes active session information through its HTTP API.
- Browser WebSocket clients can request session watches, and dashboard commands are forwarded to pi sessions; the upgrade check allows connections with no Origin header.
Source & flagged code
7 flaggedPackage source references child process execution.
extensions/image-gen/image-gen.tsView on unpkg · L15Package source references shell execution.
extensions/orchestrator/git-helpers.tsView on unpkg · L440Findings
Affected versions and remediation
This report applies to pi-orchestrator-config@4.16.0.
See all versions of pi-orchestrator-config for other recorded verdicts.
- Review the evidence and your use of pi-orchestrator-config@4.16.0 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.