pi-orchestrator-config@4.6.2
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 default-on local dashboard that forwards session content and can submit browser prompts, so a warning is appropriate. The inspected behavior is local and package-aligned, with no evidence of an external attack chain or install-time mutation.
Decision evidence
public snapshot- The manifest lists build and prepack scripts and registers the package extension tree.
- The pidash dashboard is enabled by default; its registration returns early when disabled.
- A session start connects pidash and starts a missing daemon, using a loopback WebSocket.
- Pidash forwards saved user messages and accepts browser prompts as follow-up messages in the active session.
- The UI build command runs only when the UI files are missing.
- The inspected dashboard connection is local; no publisher-controlled recipient, credential collection, destructive behavior, or install-time settings mutation was identified.
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.6.2.
See all versions of pi-orchestrator-config for other recorded verdicts.
- Review the evidence and your use of pi-orchestrator-config@4.6.2 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.