registry / linkshell-cli / 0.10.63
linkshell-cli@0.10.63
⚠ Under reviewFollow, 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-aiThe inspected install hook only adjusts permissions on node-pty helper files, and the login flow uses a loopback callback and LinkShell services. Host startup depends on an external runtime package whose behavior could not be resolved, so this review needs manual review.
Static reason
One or more suspicious static signals were detected.
Trigger
A user runs the host command or another CLI flow that starts the host.
Impact
The delegated host behavior cannot be fully assessed from the available source.
Mechanism
The CLI dynamically imports @linkshell/host to perform host operations; the imported implementation could not be reviewed here.
AI rationale
The inspected install hook only adjusts permissions on node-pty helper files, and the login flow uses a loopback callback and LinkShell services. Host startup depends on an external runtime package whose behavior could not be resolved, so this review needs manual review.
Evidence
package.jsondist/cli/src/commands/host.jsscripts/postinstall.mjsdist/cli/src/commands/login.js
Network endpoints2
itool.tech/en/auth/linkshellwss://gateway.itool.tech
Decision evidence
public snapshotAI called this Manual Review at 77.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The manifest declares a postinstall hook and dependencies on @linkshell/host, @linkshell/wire, and @linkshell/gateway.
- The postinstall hook looks for node-pty helper files and changes their permissions when present.
- The login path sends the browser-returned token to the Supabase user endpoint and saves the returned tokens locally.
- The host sends a saved token only when its configured gateway matches LinkShell’s official gateway.
- Host startup dynamically imports @linkshell/host, whose implementation is not available in this package snapshot.
Evidence against
- The inspected postinstall hook is limited to fixing node-pty helper permissions.
- The login callback uses a loopback server, and the CLI opens LinkShell’s login page. No unrelated credential recipient was established in the inspected login path.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket
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/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
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
Low
Affected versions and remediation
This report applies to linkshell-cli@0.10.63.
See all versions of linkshell-cli for other recorded verdicts.
- Review the evidence and your use of linkshell-cli@0.10.63 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.