@linzumi/cli@1.0.254
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 concrete malicious installation hook, self-dependency chain, credential theft, or destructive action was established. The opaque runtime tunnel and dynamic-code primitives leave a real unresolved capability risk, so a warning is warranted.
Decision evidence
public snapshot- The shipped tunnel bundle contains a package service endpoint and WebSocket tunnel endpoint; the large minified bundle makes complete static reachability assessment impractical.
- The main runtime contains generated code that constructs functions at runtime, increasing uncertainty in the opaque bundled artifact.
- package.json has no preinstall, install, or postinstall lifecycle hook.
- The manifest has no dependency on this package name.
- The inspected vendor script is a developer-only protocol vendoring command, not an automatic install hook.
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.254.
See all versions of @linzumi/cli for other recorded verdicts.
- Review the evidence and your use of @linzumi/cli@1.0.254 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.