registry / linkshell-cli / 0.10.60
linkshell-cli@0.10.60
Follow, steer and approve the coding agents on your computer (Claude Code, Codex, Gemini, Copilot and more) from your phone
AI Security Review
scanned 12d ago · by lpm-firewall-aiSource inspection found no concrete attack behavior. The postinstall hook performs a bounded node-pty permission fix, and the flagged runtime operations align with granted preview streaming, direct-channel handling, video signaling, and host features.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The permission adjustment runs during installation; preview, login, and host functions run when their CLI or host features are used.
Impact
No confirmed attack impact was established from the inspected behavior.
Mechanism
The hook resolves node-pty helper paths and changes permissions on files that exist. Preview connections require a valid, unexpired grant before they subscribe to session frames.
AI rationale
Source inspection found no concrete attack behavior. The postinstall hook performs a bounded node-pty permission fix, and the flagged runtime operations align with granted preview streaming, direct-channel handling, video signaling, and host features.
Evidence
scripts/postinstall.mjs
Network endpoints1
wss://gateway.itool.tech
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package postinstall runs a script that resolves node-pty and changes permissions only on existing platform helper files.
- The preview stream requires a valid, unexpired one-time grant before subscribing to that session’s frames; the observed account-action locations carry those granted frames.
- The direct channel checks its label and active connection, while video signaling handles connection feedback and ICE candidates.
- The CLI uses LinkShell gateway configuration, local host storage, and port forwarding over a device channel; login sends its token to the configured authentication service.
- Inspected dependency excerpts show Commander exports, node-pty build and cleanup hooks, pseudoterminal spawning, and the qrcode-terminal package.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket
Source & flagged code
9 flaggedpackage.jsonView file
•scripts.postinstall = node scripts/postinstall.mjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node scripts/postinstall.mjs
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgdist/host/src/ports.jsView file
1import { execFile } from "node:child_process";
L2: import { readlink } from "node:fs/promises";
High
Child Process
Package source references child process execution.
dist/host/src/ports.jsView on unpkg · L1Findings
1 Critical7 High5 Medium4 Low
CriticalPrevious Version Dangerous Deltadist/host/src/rpc/server.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processdist/host/src/ports.js
HighShell
HighCommand Output Exfiltrationdist/cli/src/commands/upgrade.js
HighSandbox Evasion Gated Capabilitydist/cli/src/commands/upgrade.js
HighTrigger Reachable Command Output Exfiltrationdist/cli/src/commands/login.js
HighSemantic Analysis Limiteddist/cli/src/commands/host.js#virtual:normalized:round1
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requiredist/cli/src/index.js
MediumNetwork
Medium
Affected versions and remediation
This report applies to linkshell-cli@0.10.60.
See all versions of linkshell-cli for other recorded verdicts.
- Review the evidence and your use of linkshell-cli@0.10.60 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.