registry / linkshell-cli / 0.10.39
linkshell-cli@0.10.39
Follow, steer and approve the coding agents on your computer (Claude Code, Codex, Gemini, Copilot and more) from your phone
AI Security Review
scanned 20d ago · by lpm-firewall-aiSource inspection resolves the lifecycle and static execution/network signals as dependency setup and user-invoked product behavior. No concrete attack behavior was found.
Static reason
One or more suspicious static signals were detected.
Trigger
Installation runs the postinstall permission fix; login, upgrade, host preview, and agent launch require their corresponding product actions.
Impact
Inspected behavior does not establish credential theft, unconsented account changes, or another attack.
Mechanism
The hook adjusts node-pty helper permissions. Login uses a browser callback and the LinkShell service; upgrade invokes npm only from its explicit command; port previews connect to loopback services.
AI rationale
Source inspection resolves the lifecycle and static execution/network signals as dependency setup and user-invoked product behavior. No concrete attack behavior was found.
Evidence
package.jsonscripts/postinstall.mjsdist/cli/src/index.jsdist/cli/src/commands/login.jsdist/cli/src/auth.jsdist/cli/src/commands/upgrade.jsdist/host/src/ports.jsdist/cli/src/commands/host.js
Network endpoints3
itool.tech/en/auth/linkshellmkbeusztkzffnzjdwmqk.supabase.coregistry.npmjs.org/linkshell-cli/latest
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json runs a postinstall hook; its source only changes permissions on node-pty helper files.
- The explicit login command starts an iTool browser flow, receives tokens through a localhost callback, checks them against the LinkShell Supabase service, and saves them locally.
- The explicit upgrade command checks npm for a newer release and invokes the package manager only when the user runs that command.
- The host discovers local HTTP services and proxies loopback connections through its device preview channel, consistent with the package’s remote terminal product.
- Agent processes are launched with inherited terminal I/O and the selected launch command and environment.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
8 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
7 High5 Medium4 Low
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processdist/host/src/ports.js
HighShell
HighCommand Output Exfiltrationdist/cli/src/commands/login.js
HighTrigger Reachable Command Output Exfiltrationdist/cli/src/commands/login.js
HighRuntime Package Installdist/cli/src/commands/upgrade.js
HighSemantic Analysis Limiteddist/cli/src/commands/host.js#virtual:normalized:round1
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requiredist/cli/src/index.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
Affected versions and remediation
This report applies to linkshell-cli@0.10.39.
See all versions of linkshell-cli for other recorded verdicts.
- Review the evidence and your use of linkshell-cli@0.10.39 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.