pi-orchestrator-config@4.7.1
Orchestrator pattern for pi: specialist subagents, enforcement, code review loop, workflow commands
AI Security Review
scanned 15d ago · by lpm-firewall-aiThe package has no install lifecycle hook, and the suspicious install command is limited to runtime UI recovery when built files are missing. Because that path can run dependency scripts automatically, unresolved execution risk warrants a warning, but the inspected source does not establish malicious behavior.
Decision evidence
public snapshot- When a UI file is missing, serving it can automatically run `npm install` and `npm run build` in the UI source directory.
- The manifest defines only a `prepack` build hook; the install command is reachable at runtime when the UI is missing.
- Pidash is disabled unless project settings enable it, and its WebSocket client connects to loopback.
- Image generation is an explicit tool that sends its request and API key to the intended Gemini API endpoint.
- Session validation runs on session start and checks CLI availability; the inspected code does not establish a malicious action.
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.1.
See all versions of pi-orchestrator-config for other recorded verdicts.
- Review the evidence and your use of pi-orchestrator-config@4.7.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.