@gigaflow/gmux@0.16.0
gmux — an LLM-native layer over your tmux workspace: browse, search and resume your AI coding agent sessions across Claude Code, Codex, and any other harness.
AI Security Review
scanned 2d ago · by lpm-firewall-aiWithout a config file, gmux enables background summaries by default and uses an available model CLI, even on the noninteractive path that skips setup. That can spend the user’s provider tokens and send session content without an explicit request, so this meets the rule for malicious automatic spending.
Decision evidence
public snapshot- Most CLI actions automatically trigger a detached background summarization pass.
- When no config exists, gmux treats background summarization as allowed and selects a detected model CLI, falling back to `claude -p`.
- The pass sends distilled coding-session details to the provider CLI; the package documents that background model calls spend tokens.
- The package has no install, preinstall, or postinstall hook; its only publish lifecycle script is `prepublishOnly`.
- Interactive setup asks whether to enable background summaries and discloses token use, but the no-config, noninteractive path bypasses that prompt.
- Summarization supports gmux’s stated purpose of helping developers resume coding sessions.
- The configured provider is an installed model CLI, and the setup prompt discloses the token cost.
- Users can disable background calls with `GMUX_AUTO_SUMMARIZE=0`.
Source & flagged code
5 flaggedPackage source references child process execution.
dist/cli/picker.jsView on unpkg · L13Package source references weak cryptographic algorithms.
dist/services/sensors.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @gigaflow/gmux@0.16.0.
See all versions of @gigaflow/gmux for other recorded verdicts.
- Avoid installing @gigaflow/gmux@0.16.0. 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.