@linzumi/cli@1.0.235
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-aiSource inspection found no registry-install lifecycle trigger or concrete malicious chain. The flagged execution and network primitives are bounded or aligned with explicit CLI functionality.
Decision evidence
public snapshot- The manifest exposes a CLI and build-related scripts.
- A developer-only vendoring script names an OpenAI Git source.
- The TypeScript bundle uses an evaluated worker for a bounded filesystem responsiveness probe.
- The runtime can locate a user-selected Codex home directory.
- The tunnel component contains Linzumi service endpoints.
- No preinstall, install, or postinstall lifecycle hook is declared.
- The evaluated worker only calls statSync on a supplied path.
- The vendoring code is an explicit development script, not an install trigger.
- Network and local-agent access are reached through explicit CLI functionality; no secret theft, remote payload execution, or broad agent-control mutation was confirmed.
Source & flagged code
16 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.235.
See all versions of @linzumi/cli for other recorded verdicts.
- Review the evidence and your use of @linzumi/cli@1.0.235 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.