pi-orchestrator-config@4.5.0
Orchestrator pattern for pi: specialist subagents, enforcement, code review loop, workflow commands
AI Security Review
scanned 15d ago · by lpm-firewall-aiSource inspection found no install-time attack, but the default-enabled dashboard exposes session viewing and prompt submission on a network-wide listener without authentication in the inspected WebSocket path. This is an unresolved capability risk, so warn rather than block.
Decision evidence
public snapshot- Pidash is enabled by default and connects during a TUI session start.
- Pidash forwards Pi events to its daemon, including agent and message events.
- The daemon listens on all interfaces and permits WebSocket upgrades when the Origin header is absent; browser clients can watch sessions and receive buffered events.
- Browser messages can be forwarded as prompts to a connected Pi session.
- Pidash is a package feature intended to provide a browser dashboard; the source restricts supplied Origin headers to localhost or private-network addresses.
- The Pi extension connects to the daemon over loopback, and no credential theft or unrelated publisher-controlled recipient was found in the inspected path.
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/session-validation.tsView on unpkg · L206Findings
Affected versions and remediation
This report applies to pi-orchestrator-config@4.5.0.
See all versions of pi-orchestrator-config for other recorded verdicts.
- Review the evidence and your use of pi-orchestrator-config@4.5.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.