triflux@10.55.1
CLI-first multi-model orchestrator for Claude Code — route tasks to Codex, Antigravity, and Claude
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe postinstall hook activates setup that changes agent configuration without obtaining consent, matching the install-time control-surface policy. The observed writes support blocking even though the configuration is for Triflux features.
Decision evidence
public snapshot- package.json runs scripts/setup.mjs automatically on postinstall.
- The installed package invokes runDeferred during postinstall; its setup flow does not require an interactive terminal.
- runDeferred reads and changes Claude settings through applyStatusLine, applyAgentTeams, and applyRemoteControl, then persists changes.
- The setup path also invokes Codex hook setup, which writes hooks.json when its managed hooks change.
- The source therefore establishes unconsented install-time changes to AI-agent configuration.
- The setup functions use package-owned Triflux integrations, and Codex hook installation is separately consent-gated in the interactive setup flow.
Source & flagged code
13 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.55.1.
See all versions of triflux for other recorded verdicts.
- Avoid installing triflux@10.55.1. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.