registry / linkshell-cli / 0.10.75
linkshell-cli@0.10.75
Follow, steer and approve the coding agents on your computer (Claude Code, Codex, Gemini, Copilot and more) from your phone
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe install hook only fixes permissions on node-pty spawn helpers. The flagged network and credential flows are tied to explicit upgrade and login commands, and the upgrade worker stores output locally.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The permission adjustment runs during installation; version checks and credential use occur through explicit upgrade and login commands.
Impact
No unsolicited data transfer, credential theft, or unrelated command execution was identified.
Mechanism
The install hook chmods node-pty helpers. Upgrade checks npm metadata and writes its worker output locally. Login sends the submitted grant to the configured LinkShell auth proxy.
AI rationale
The install hook only fixes permissions on node-pty spawn helpers. The flagged network and credential flows are tied to explicit upgrade and login commands, and the upgrade worker stores output locally.
Evidence
node-pty/prebuilds/{darwin-arm64,darwin-x64,linux-x64,linux-arm64}/spawn-helperlinkshellDir()/upgrade.log
Network endpoints6
registry.npmjs.org/linkshell-cli/latestitool.tech/api/linkshell/auth${SUPABASE_URL}/auth/v1/token?grant_type=…${SUPABASE_URL}/auth/v1/user${SUPABASE_URL}/rest/v1/profilesitool.tech/api/pro/redeem
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package postinstall runs a script that adjusts permissions on existing node-pty spawn helpers.
- The upgrade command fetches only the latest package version from npm; running it requires invoking `linkshell upgrade`.
- The upgrade worker saves command output to a local `upgrade.log` file.
- The sign-in flow sends a grant to the LinkShell auth proxy during an explicit login flow; this credential use is not triggered by install or import.
Evidence against
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/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
Medium
Affected versions and remediation
This report applies to linkshell-cli@0.10.75.
See all versions of linkshell-cli for other recorded verdicts.
- Review the evidence and your use of linkshell-cli@0.10.75 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.