pi-orchestrator-config@4.22.2
Orchestrator pattern for pi: specialist subagents, enforcement, code review loop, workflow commands
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe manifest contains no install lifecycle hook, and the reviewed credential flow sends a Google API key to Google only as part of an explicitly invoked image-generation tool. Runtime build and shell execution are tied to UI serving and configured enforcement features; the flagged source did not establish an attack.
Decision evidence
public snapshot- The manifest has build and typecheck scripts, but no install lifecycle hook.
- Image generation is exposed as an explicit tool and requires a configured image model and Google API key.
- The image tool sends its request and API key to Google’s Gemini API, matching its documented purpose.
- The UI build command runs only when the UI is missing or unreadable and its package manifest exists.
- The pidash extension handles session_start and may initialize a dashboard connection automatically.
- Serving a missing UI can invoke npm install and build at runtime.
- Enforcement actions can execute configured shell commands.
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/git-helpers.tsView on unpkg · L440Findings
Affected versions and remediation
This report applies to pi-orchestrator-config@4.22.2.
See all versions of pi-orchestrator-config for other recorded verdicts.
- Review the evidence and your use of pi-orchestrator-config@4.22.2 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.