@linzumi/cli@1.0.247
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 installation-time attack or opaque remote code execution was confirmed. The package nevertheless provides concrete authenticated agent-control and secret-access capabilities, so it should be warned pending trust review of the service and intended deployment.
Decision evidence
public snapshot- Runtime code sends bearer-authenticated requests to Linzumi personal-agent or local-runner APIs.
- The API client exposes vault-secret retrieval and agent child-job operations.
- The cloud supervisor reads a local Linzumi authentication cache and uses its access token.
- The TCP tunnel command uses Linzumi-hosted WebSocket and service endpoints.
- package.json has no preinstall, install, or postinstall hook.
- The risky capabilities are reached through the user-invoked CLI, not package installation.
- The development vendoring script runs only through an explicit npm script and invokes git with argument arrays.
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.247.
See all versions of @linzumi/cli for other recorded verdicts.
- Review the evidence and your use of @linzumi/cli@1.0.247 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.