triflux@10.76.1
CLI-first multi-model orchestrator for Claude Code — route tasks to Codex, Antigravity, and Claude
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe postinstall prepares Codex hooks without affirmative approval during noninteractive installation, creating an agent extension lifecycle risk. Source shows that the hooks remain untrusted pending Codex approval and record session metadata locally, so the evidence supports a warning rather than a block.
Decision evidence
public snapshot- The npm postinstall starts the deferred setup flow from scripts/setup.mjs.
- Setup adds Codex SessionStart and UserPromptSubmit hooks and updates Codex hook configuration.
- The hook installer does not preapprove the hooks; it leaves approval to Codex, and setup defers approval when it cannot ask the user.
- When run, the hook records Codex session and terminal metadata in a local registry.
- The supplied CLI, cleanup, MCP, model-resolver, and live-CLI excerpts concern local configuration or state; those excerpts do not establish credential transfer or account changes.
- The hooks are first-party package functionality, and their recorded session metadata is written locally.
- The inspected installer leaves the hooks untrusted until Codex prompts for approval.
Source & flagged code
25 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgPackage source references shell execution.
Findings
Affected versions and remediation
This report applies to triflux@10.76.1.
See all versions of triflux for other recorded verdicts.
- Review the evidence and your use of triflux@10.76.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.