@linzumi/cli@1.0.232
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 3mo ago · by lpm-firewall-aiThe malicious scanner findings overstate bundled dependency primitives and an explicit TCP-forwarding feature. Source inspection found no lifecycle hook or concrete malicious execution chain.
Decision evidence
public snapshot- No npm preinstall, install, or postinstall hook is declared.
- The executable only imports and invokes the bundled CLI after a user runs `linzumi`.
- The TCP component documents a user-invoked loopback listener; no remote asset decode-and-execute path was found.
- Runtime CLI code uses network, local files, subprocesses, and user-provided credentials for its stated agent-runner functionality.
- The bundle contains an `eval` reference from bundled dependencies, but inspection found no package-controlled remote payload execution.
Source & flagged code
17 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.232.
See all versions of @linzumi/cli for other recorded verdicts.
- Review the evidence and your use of @linzumi/cli@1.0.232 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.