pi-orchestrator-config@4.8.4
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 lifecycle hook or confirmed malicious behavior. The flagged execution and network use align with image generation, local UI building, Git queries, and pidash's loopback session dashboard.
Decision evidence
public snapshot- package.json defines only build and prepack scripts; it has no install lifecycle hook.
- Image generation reads a caller's Google API key and sends it to Google's Gemini API.
- Git helpers run Git queries with a five-second timeout; the inspected callers use fixed Git arguments.
- The UI build runs only when its dist page is missing and a local UI package.json exists.
- Pidash connects to a loopback WebSocket during session startup and forwards session events to that local daemon.
- The acpx loader searches global and package-local acpx installations and imports the runtime.
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 · L446Findings
Affected versions and remediation
This report applies to pi-orchestrator-config@4.8.4.
See all versions of pi-orchestrator-config for other recorded verdicts.
- Review the evidence and your use of pi-orchestrator-config@4.8.4 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.