registry / linkshell-cli / 0.10.5
linkshell-cli@0.10.5
Follow, steer and approve the coding agents on your computer (Claude Code, Codex, Gemini, Copilot and more) from your phone
AI Security Review
scanned 27d ago · by lpm-firewall-aiInspected the lifecycle hook and required flagged source paths. Their behavior is consistent with package setup, local host discovery, intended-service authentication, and a user-invoked upgrade; no concrete malicious chain was found.
Static reason
One or more suspicious static signals were detected.
Trigger
Installation runs the postinstall helper; login, host, and upgrade behavior requires invoking their respective commands.
Impact
No concrete malicious effect or confirmed attack surface was established.
Mechanism
The helper adjusts node-pty permissions, host discovery inspects local listeners, login authenticates with Supabase, and upgrade checks npm before installing an update.
AI rationale
Inspected the lifecycle hook and required flagged source paths. Their behavior is consistent with package setup, local host discovery, intended-service authentication, and a user-invoked upgrade; no concrete malicious chain was found.
Evidence
package.jsonscripts/postinstall.mjsdist/host/src/ports.jsdist/cli/src/commands/login.jsdist/cli/src/commands/upgrade.jsdist/cli/src/commands/host.js
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall hook runs a package-local script; inspection showed it only fixes permissions on node-pty helper files.
- Host discovery uses platform tools to list listening TCP ports; inspected connection code targets loopback addresses.
- Login sends the received access token to the configured Supabase authentication service for user information.
- Upgrade checks for a new version and installs it only when the user invokes the upgrade command.
- The host sends its account token only when connected to LinkShell’s official gateway.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
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/login.js
HighTrigger Reachable Command Output Exfiltrationdist/cli/src/commands/login.js
HighRuntime Package Installdist/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
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
Affected versions and remediation
This report applies to linkshell-cli@0.10.5.
See all versions of linkshell-cli for other recorded verdicts.
- Review the evidence and your use of linkshell-cli@0.10.5 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.