registry / linkshell-cli / 0.10.57
linkshell-cli@0.10.57
Follow, steer and approve the coding agents on your computer (Claude Code, Codex, Gemini, Copilot and more) from your phone
AI Security Review
scanned 13d ago · by lpm-firewall-aiSource inspection found a package-aligned permission fix and user-invoked authentication and remote-session behavior. The scanner’s execution and network signals correspond to those features, with no confirmed attack behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Package installation runs the postinstall hook; login and host features run when a user invokes them.
Impact
No unrelated credential disclosure or unrequested account action was established.
Mechanism
The hook adjusts permissions for existing node-pty helper files. Login uses a loopback callback, and the host sends account credentials only to the official LinkShell gateway.
AI rationale
Source inspection found a package-aligned permission fix and user-invoked authentication and remote-session behavior. The scanner’s execution and network signals correspond to those features, with no confirmed attack behavior.
Evidence
scripts/postinstall.mjs
Network endpoints1
itool.tech
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package install hook only sets executable permissions on bundled node-pty spawn helpers, and the node-pty hooks shown are installer/build setup.
- Login accepts a callback on loopback and checks the supplied token with the configured Supabase authentication service before saving it.
- The host forwards an account token only when using LinkShell’s official gateway; local port discovery uses standard platform utilities.
Evidence against
- The CLI runs local agent sessions and can expose them through a gateway, which is its stated product behavior; the inspected sources show no unrelated account action or credential export.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
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/cli/src/commands/desktop.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.57.
See all versions of linkshell-cli for other recorded verdicts.
- Review the evidence and your use of linkshell-cli@0.10.57 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.