pi-orchestrator-config@4.3.8
Orchestrator pattern for pi: specialist subagents, enforcement, code review loop, workflow commands
AI Security Review
scanned 15d ago · by lpm-firewall-aiSource inspection found package-aligned runtime behavior and no install-time attack. The flagged process and network operations are bounded to the described features, including dashboard forwarding to a loopback daemon.
Decision evidence
public snapshot- The manifest runs a UI build during prepack and declares the package’s Pi extensions; it has no install lifecycle hook.
- The image tool reads a Gemini key from the environment and sends image-generation requests to Google’s Gemini API.
- Session validation checks for the uv command at session start.
- The UI server runs npm install and a build only in its missing-UI fallback.
- Pidash forwards session history to a daemon configured to listen on loopback; no unrelated collector was identified.
- Pidash replays session message content to its dashboard connection.
- The UI fallback can run npm install and a build at runtime.
- Session validation invokes a shell command to check whether uv is available.
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 · L200Findings
Affected versions and remediation
This report applies to pi-orchestrator-config@4.3.8.
See all versions of pi-orchestrator-config for other recorded verdicts.
- Review the evidence and your use of pi-orchestrator-config@4.3.8 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.