registry / linkshell-cli / 0.10.30
linkshell-cli@0.10.30
Follow, steer and approve the coding agents on your computer (Claude Code, Codex, Gemini, Copilot and more) from your phone
AI Security Review
scanned 21d ago · by lpm-firewall-aiSource inspection ties the flagged primitives to package features and explicit user actions. The install hook only adjusts node-pty helper permissions, and the reviewed credential forwarding path restricts account tokens to the official gateway.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Installation runs the helper-permission adjustment; login, upgrade, host previews, and screen viewing are activated through their respective CLI or host flows.
Impact
No unauthorized credential disclosure, harmful install-time mutation, or other concrete attack behavior was established.
Mechanism
The install hook adjusts node-pty helper permissions. Login returns tokens to a local callback for validation against the configured service, while gateway token forwarding is restricted to the official gateway. Preview and screen code discovers local services and uses a gated loopback viewer.
AI rationale
Source inspection ties the flagged primitives to package features and explicit user actions. The install hook only adjusts node-pty helper permissions, and the reviewed credential forwarding path restricts account tokens to the official gateway.
Network endpoints3
itool.tech/en/auth/linkshellmkbeusztkzffnzjdwmqk.supabase.coregistry.npmjs.org/linkshell-cli/latest
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest runs a postinstall script that locates node-pty helpers and adjusts their permissions.
- Login is an explicit CLI action; browser-returned tokens are checked against the package's configured Supabase service.
- The host supplies an account token only when its gateway matches the official LinkShell gateway.
- Upgrade runs only through the explicit `linkshell upgrade` command.
- Port preview discovers and probes local web servers; screen viewing uses a loopback listener and a random token.
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/host/src/screen.js
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
Affected versions and remediation
This report applies to linkshell-cli@0.10.30.
See all versions of linkshell-cli for other recorded verdicts.
- Review the evidence and your use of linkshell-cli@0.10.30 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.