pi-orchestrator-config@4.7.0
Orchestrator pattern for pi: specialist subagents, enforcement, code review loop, workflow commands
AI Security Review
scanned 15d ago · by lpm-firewall-aiThe inspected manifest has no install hook, and the flagged execution and network behavior is conditional runtime functionality directed at the intended Gemini API or a local dashboard. The source provides no evidence of unconsented collection, credential export, or other concrete attack behavior.
Decision evidence
public snapshot- package.json defines only build and prepack scripts; it has no install lifecycle hook.
- Image generation requires a configured model and sends the generated prompt to Google’s Gemini API when the tool is invoked.
- The session validation shell check receives fixed command names at its callers; release notes are fetched with gh only after a version change.
- The UI server attempts npm install and build only when the UI is missing, as part of serving that UI.
- Pidash is disabled unless enabled in project settings, and its session relay connects to the local 127.0.0.1 daemon.
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.0.
See all versions of pi-orchestrator-config for other recorded verdicts.
- Review the evidence and your use of pi-orchestrator-config@4.7.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.