triflux@10.47.0
CLI-first multi-model orchestrator for Claude Code — route tasks to Codex, Antigravity, and Claude
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe code forwards an existing hub token to an unrestricted TFX_HUB_URL when headless session registration runs. Because this is conditional on endpoint configuration and the default is loopback, the evidence supports a warning for credential exposure rather than a block.
Decision evidence
public snapshot- hub/team/synapse-http.mjs reads the hub token from TFX_HUB_TOKEN or the user’s .claude token file.
- hub/team/synapse-http.mjs accepts TFX_HUB_URL without restricting its destination; absent that setting, it uses loopback.
- hub/team/synapse-http.mjs attaches the hub token as a Bearer authorization header and sends the request with fetch.
- hub/team/headless.mjs registers workers through the Synapse session helper, making this path reachable during headless orchestration.
- The default Synapse destination is the local hub at 127.0.0.1:27888.
- The token is described and used as hub authentication; the inspected code does not establish that a remote destination is enabled by default.
Source & flagged code
15 flagged · loading sourceA single source file combines environment access, network access, and code or shell execution; review context before blocking.
Findings
Affected versions and remediation
This report applies to triflux@10.47.0.
See all versions of triflux for other recorded verdicts.
- Review the evidence and your use of triflux@10.47.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.