pi-orchestrator-config@4.3.14
Orchestrator pattern for pi: specialist subagents, enforcement, code review loop, workflow commands
AI Security Review
scanned 15d ago · by lpm-firewall-aiInspected source supports normal package functionality, and the manifest has no install lifecycle hook. The scanner’s flagged commands are bounded to UI rebuilding and local process or worktree inspection; no concrete attack behavior was established.
Decision evidence
public snapshot- package.json defines only build and prepack scripts; prepack runs the UI build.
- The bundled pidiff UI connects to a WebSocket on the browser’s current host.
- Image generation sends requests to Google’s Gemini API.
- Cron code invokes PowerShell only to read a process start time, and autocomplete uses git to inspect worktrees.
- The UI server runs npm install and build only in its missing-UI fallback.
- Scanner flags identify dynamic loading, shell execution, and runtime installation, but inspected source ties these to bundled UI code, process identity checks, worktree completion, or rebuilding missing UI assets.
Source & flagged code
8 flaggedPackage source references child process execution.
extensions/image-gen/image-gen.tsView on unpkg · L15Package source references shell execution.
extensions/orchestrator/cron-store.tsView on unpkg · L41Findings
Affected versions and remediation
This report applies to pi-orchestrator-config@4.3.14.
See all versions of pi-orchestrator-config for other recorded verdicts.
- Review the evidence and your use of pi-orchestrator-config@4.3.14 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.