pi-orchestrator-config@4.4.0
Orchestrator pattern for pi: specialist subagents, enforcement, code review loop, workflow commands
AI Security Review
scanned 15d ago · by lpm-firewall-aiInspected source shows no install lifecycle hook or confirmed attack. The flagged network and execution primitives support package functionality and are activated by user-facing image generation or a missing local UI build.
Decision evidence
public snapshot- package.json defines only build and prepack scripts; it has no install lifecycle hook.
- The image tool sends its prompt to Google’s Gemini API using an API key supplied through the environment.
- Cron process identity uses a fixed PowerShell command through execFileSync.
- The UI server runs npm install and a build only when its UI files are missing.
- Git helpers use shell execution for git commands; the inspected source shows no separate malicious action.
- The logger dynamically loads the package’s project settings to choose a log level.
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.0.
See all versions of pi-orchestrator-config for other recorded verdicts.
- Review the evidence and your use of pi-orchestrator-config@4.4.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.