pi-orchestrator-config@4.6.4
Orchestrator pattern for pi: specialist subagents, enforcement, code review loop, workflow commands
AI Security Review
scanned 15d ago · by lpm-firewall-aiThe inspected findings are consistent with package functionality, and package.json has no install lifecycle hook. The pidash daemon is disabled unless configured and defaults to loopback; no concrete attack behavior was established.
Decision evidence
public snapshot- package.json declares only build and prepack scripts, with no install lifecycle hook.
- Image generation is exposed as a tool and sends requests to Google’s Gemini API.
- Session validation checks for fixed CLI names on PATH; its shell command is used for availability checks.
- The UI server attempts a build when its dist files are missing.
- Pidash is disabled unless the project setting enables it, and its daemon defaults to listening on 127.0.0.1.
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.4.
See all versions of pi-orchestrator-config for other recorded verdicts.
- Review the evidence and your use of pi-orchestrator-config@4.6.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.