registry / linkshell-cli / 0.10.71
linkshell-cli@0.10.71
⚠ 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 10d ago · by lpm-firewall-aiThe inspected postinstall hook performs a targeted node-pty permission fix, and the flagged login behavior does not establish command-output exfiltration. Selected runtime dependencies remain unresolved in this snapshot, so the package cannot be marked clean.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Use of CLI host operations that dynamically load @linkshell/host.
Impact
The unresolved dependency behavior prevents a clean determination, but the inspected source does not establish an attack.
Mechanism
The package manifest selects external @linkshell runtime dependencies, and the CLI imports the host package during host operations; its implementation could not be reviewed here.
AI rationale
The inspected postinstall hook performs a targeted node-pty permission fix, and the flagged login behavior does not establish command-output exfiltration. Selected runtime dependencies remain unresolved in this snapshot, so the package cannot be marked clean.
Evidence
package.jsondist/cli/src/index.jsdist/cli/src/commands/host.js
Decision evidence
public snapshotAI called this Manual Review at 81.0% confidence as Unknown with medium false-positive risk.
AI review observations
- package.json selects @linkshell/host, @linkshell/wire, and @linkshell/gateway as runtime dependencies.
- The CLI dynamically imports @linkshell/host for host operations; that implementation is not present in the inspected package source, leaving selected runtime behavior unresolved.
- The inspected login flow validates the returned account token against the configured service, and the postinstall hook only changes permissions on node-pty helper files.
Evidence against
- The inspected postinstall source only applies execute permissions to node-pty helper files.
- The flagged login process launches a browser with stdio ignored and receives its callback on loopback; the inspected code does not establish command-output exfiltration.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStrings
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/host.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.71.
See all versions of linkshell-cli for other recorded verdicts.
- Review the evidence and your use of linkshell-cli@0.10.71 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.