pi-orchestrator-config@4.6.0
Orchestrator pattern for pi: specialist subagents, enforcement, code review loop, workflow commands
AI Security Review
scanned 15d ago · by lpm-firewall-aiThe manifest has no install hook, and the flagged runtime calls are tied to a user-facing feature, a fixed session check, or a missing-UI build fallback. The inspected network destinations and activation paths do not establish a concrete attack.
Decision evidence
public snapshot- package.json defines only UI build and prepack scripts; it has no install lifecycle hook.
- Image generation is exposed as a named tool and sends its request with an API key to Google's Gemini API.
- At session start, session validation checks for the fixed `uv` command.
- The UI build fallback runs only when the UI output is missing and its source directory contains a package manifest.
- Pidash connects to a loopback WebSocket daemon and registers session metadata there.
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.0.
See all versions of pi-orchestrator-config for other recorded verdicts.
- Review the evidence and your use of pi-orchestrator-config@4.6.0 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.