linkshell-cli@0.10.72
Follow, steer and approve the coding agents on your computer (Claude Code, Codex, Gemini, Copilot and more) from your phone
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe scanner’s install, process, and network signals resolve to expected terminal setup, user-invoked CLI behavior, and service authentication. Inspected source did not establish a concrete attack surface.
Decision evidence
public snapshot- The package postinstall only adds execute permission to existing node-pty helper binaries; it does not run a download or command.
- The node-pty install scripts check for platform prebuilds, fall back to a native build, and clean build output; its runtime exports pseudoterminal operations.
- The login flow validates received tokens with the package’s configured Supabase service, while the CLI stores them locally with restrictive file permissions.
- The host sends a cached account token only when the selected gateway matches LinkShell’s official gateway; the inspected store defines ordinary session records.
- The inspected CLI and dependencies show normal command dispatch, update lookup, and library entrypoints; no concrete attack behavior was identified.
Source & flagged code
9 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage source references child process execution.
dist/host/src/ports.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to linkshell-cli@0.10.72.
See all versions of linkshell-cli for other recorded verdicts.
- Review the evidence and your use of linkshell-cli@0.10.72 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.