pi-orchestrator-config@4.4.1
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 lifecycle hook, and the inspected runtime behaviors are tied to package features and their stated triggers. Scanner flags for process execution and runtime UI installation do not establish malicious behavior in the inspected source.
Decision evidence
public snapshot- package.json lists build and prepack scripts; it has no install lifecycle hook.
- The image tool sends a caller-provided prompt and environment API key to Google’s Gemini generation endpoint.
- Cron process-token code reads OS process metadata and uses PowerShell only to obtain a process start time on Windows.
- The UI helper runs npm install and a build only when the UI files are missing, in the UI source directory.
- Pidash connects on session start and opens a WebSocket to the local daemon at 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/cron-store.tsView on unpkg · L41Findings
Affected versions and remediation
This report applies to pi-orchestrator-config@4.4.1.
See all versions of pi-orchestrator-config for other recorded verdicts.
- Review the evidence and your use of pi-orchestrator-config@4.4.1 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.