@linzumi/cli@1.0.259
Linzumi CLI — point a Codex agent at the real code on your laptop, with your team watching and steering from shared threads.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is not a confirmed malicious install chain because there are no package lifecycle hooks. The explicit relay and dynamic compilation capabilities leave a meaningful, unresolved runtime risk.
Decision evidence
public snapshot- The CLI dispatches an explicit tcpConnect command into a TCP relay module.
- The relay module creates a local server and sends binary frames over a tunnel WebSocket.
- The shipped cloud-supervisor bundle dynamically compiles generated JavaScript.
- A development-only vendor script can clone a configurable Git source and run local tooling when explicitly invoked.
- package.json has no preinstall, install, postinstall, or prepare lifecycle hook.
- The risky networking and process features are reached through explicit CLI or development-script commands, not package installation.
Source & flagged code
18 flaggedPackage source references child process execution.
scripts/vendor-codex-app-server-protocol.tsView on unpkg · L13A single source file combines environment access, network access, and code or shell execution with blocking evidence.
Findings
Affected versions and remediation
This report applies to @linzumi/cli@1.0.259.
See all versions of @linzumi/cli for other recorded verdicts.
- Review the evidence and your use of @linzumi/cli@1.0.259 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.