registry / linkshell-cli / 0.10.53
linkshell-cli@0.10.53
⚠ 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 14d ago · by lpm-firewall-aiThe inspected lifecycle and login behavior are consistent with package setup and intended authentication, with no confirmed attack found. The selected runtime dependency node-pty could not be inspected in the supplied dependency snapshot, so a clean verdict is not supported.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Using the host terminal feature loads node-pty.
Impact
Behavior inside the unresolved dependency cannot be assessed from the inspected bytes; no harmful effect is confirmed.
Mechanism
The manifest and terminal source show the dependency and its use, but its source was unresolved in the supplied snapshot. The inspected install hook only adjusts permissions on existing helper files.
AI rationale
The inspected lifecycle and login behavior are consistent with package setup and intended authentication, with no confirmed attack found. The selected runtime dependency node-pty could not be inspected in the supplied dependency snapshot, so a clean verdict is not supported.
Evidence
package.jsonscripts/postinstall.mjsdist/host/src/terminals.js
Decision evidence
public snapshotAI called this Manual Review at 78.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The postinstall hook resolves node-pty helpers and sets executable permissions on existing candidates.
- The login callback uses the access token for a user lookup at the configured Supabase endpoint.
- Usage collection reads agent session logs and produces token-count records; no outbound transfer was found in that code.
- The manifest selects node-pty as a runtime dependency, and the host imports it for terminal creation.
Evidence against
- The supplied dependency snapshot marks node-pty@1.1.0 unresolved, so its runtime behavior could not be assessed.
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.53.
See all versions of linkshell-cli for other recorded verdicts.
- Review the evidence and your use of linkshell-cli@0.10.53 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.