linkshell-cli@0.10.66
Follow, steer and approve the coding agents on your computer (Claude Code, Codex, Gemini, Copilot and more) from your phone
AI Security Review
scanned 11d ago · by lpm-firewall-aiSource inspection shows a package-aligned postinstall permission fix, native pseudoterminal setup, and an account login flow that validates tokens with the configured account service. The scanner’s command execution and network signals match these product behaviors; no concrete attack behavior was confirmed.
Decision evidence
public snapshot- The package postinstall adjusts permissions on node-pty helper files; the inspected hook does not collect or send data.
- The inspected node-pty install scripts check or prepare native terminal artifacts, and its exported spawn function starts a pseudoterminal process.
- Login sends the browser to the package’s account page, receives tokens through a loopback callback, and validates them against the configured account service.
- Desktop actions use named CLI actions and typed host RPC calls for product functions such as pairing and screen access.
- The inspected host code gates token forwarding on using the official gateway, lists local listening ports, stores host state locally, and checks the package’s release version through the npm registry.
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.66.
See all versions of linkshell-cli for other recorded verdicts.
- Review the evidence and your use of linkshell-cli@0.10.66 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.