@linzumi/cli@1.0.256
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-aiNo automatic installation behavior or concrete malware action was found. The remote agent and credential-persistence capability remains a real, incompletely auditable risk.
Decision evidence
public snapshot- The CLI dynamically loads a TCP tunnel module for user-invoked login and connection commands.
- The bundled tunnel module defines Linzumi WebSocket and service endpoints.
- The cloud supervisor accepts an MCP authentication value and writes it to a cloud guest filesystem.
- The published package contains large bundled runtime artifacts whose full cloud-agent data flow is not readily auditable statically.
- package.json has no preinstall, install, or postinstall hook.
- The executable is activated through the linzumi command, not on package installation.
- No source fact established covert credential exfiltration, remote payload evaluation, or destructive action.
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.256.
See all versions of @linzumi/cli for other recorded verdicts.
- Review the evidence and your use of @linzumi/cli@1.0.256 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.