@linzumi/cli
Linzumi CLI — point a Codex agent at the real code on your laptop, with your team watching and steering from shared threads.
This report shows the evidence for @linzumi/cli@1.0.311. 1 of 149 known versions is blocked or flagged. The newest version, 1.0.328, is allowed. See all versions.
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe CLI routes Anthropic API-key authentication through Linzumi’s proxy in applicable agent contexts, sending a third-party provider credential to the package vendor without clear disclosure or consent. This meets the credential-exfiltration rule despite the otherwise legitimate CLI purpose.
Decision evidence
public snapshot- The CLI detects ANTHROPIC_API_KEY or ANTHROPIC_AUTH_TOKEN and routes user API key credentials through the LlmProxy lane when a proxy binding applies.
- The proxy provider is named “Linzumi Proxy” and sends model requests to the configured proxy base URL at /v1.
- The executable entry point calls main() with the user’s CLI arguments; the README describes signing in and connecting to a Linzumi workspace.
- The package sets https://serve.linzumi.com as its default service endpoint.
- The package has no install, preinstall, or postinstall hook.
- The package is a documented local coding-agent CLI, so model-provider requests are part of its stated purpose.
- The credential routing occurs in the model-provider path rather than as an install-time action.
Source & flagged code
20 flaggedPackage source references child process execution.
dist/topics-cli.mjsView on unpkg · L3A single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/topics-cli.mjsView on unpkg · L2Source combines command execution, command-output handling, and outbound requests; review data flow before blocking.
dist/topics-cli.mjsView on unpkg · L3Source appears to send environment or credential material to an external endpoint.
dist/cloud-supervisor.mjsView on unpkg · L2Source reaches cloud instance metadata or link-local credential endpoints.
dist/cloud-supervisor.mjsView on unpkg · L2Source exposes local file and command tools to a remote model endpoint.
dist/cloud-supervisor.mjsView on unpkg · L3Source spawns a local helper that also contains network and dynamic execution context; review data flow before blocking.
dist/cloud-supervisor.mjsView on unpkg · L2Package source references dynamic require/import behavior.
dist/cloud-supervisor.mjsView on unpkg · L1Package source references weak cryptographic algorithms.
dist/cloud-supervisor.mjsView on unpkg · L2Source fetches a remote non-code asset, decodes its contents, and dynamically executes the decoded payload.
dist/index.jsView on unpkg · L2A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
dist/index.jsView on unpkg · L3Manifest-reachable source sends a prompted API credential to a fixed unofficial gateway and persists the redirection.
dist/index.jsView on unpkgA manifest entrypoint or package-local install chain reaches command-output exfiltration behavior.
dist/index.jsView on unpkg · L3Package source invokes a package manager install command at runtime.
dist/index.jsView on unpkg · L167A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/index.jsView on unpkgPackage contains source files above the normal full-analysis size ceiling.
dist/index.jsView on unpkgPackage ships native binary artifacts.
native/darwin/linzumi-terminal-pty-helperView on unpkgPackage ships non-JavaScript build or shell helper files.
scripts/codex-wire-canary.shView on unpkgFindings
Affected versions and remediation
This report applies to @linzumi/cli@1.0.311.
The versions list below shows the verdict for each recorded version.
- Avoid installing @linzumi/cli@1.0.311. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.
Versions
149 known versionsShowing the 100 most recent of 149 known versions.