pi-orchestrator-config@4.7.3
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 concrete malicious behavior. The flagged commands are tied to feature-specific runtime or UI build paths, and pidash communicates with its local daemon.
Decision evidence
public snapshot- package.json defines only build and prepack scripts; it has no install lifecycle hook.
- The image generation API runs as a tool, requires a configured model and API key, and sends requests to Google’s Gemini API.
- Session validation uses shell execution only to check whether a named CLI command is available.
- The UI helper builds assets only when the UI index is missing and a UI package manifest exists.
- Pidash connects to a loopback WebSocket; incoming prompts are forwarded as user messages.
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 · L205Findings
Affected versions and remediation
This report applies to pi-orchestrator-config@4.7.3.
See all versions of pi-orchestrator-config for other recorded verdicts.
- Review the evidence and your use of pi-orchestrator-config@4.7.3 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.