registry / linkshell-cli / 0.10.32
linkshell-cli@0.10.32
Follow, steer and approve the coding agents on your computer (Claude Code, Codex, Gemini, Copilot and more) from your phone
AI Security Review
scanned 20d ago · by lpm-firewall-aiSource inspection found no concrete attack behavior. The scanner's flagged login, process, and network signals correspond to user-invoked product functions or package-aligned setup.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Login and upgrade behavior starts when a user invokes the corresponding CLI command; the permission adjustment runs during postinstall.
Impact
The inspected behavior does not establish unauthorized data transfer or an attack on the consumer.
Mechanism
Login handles LinkShell account tokens through a local callback and Supabase. The postinstall hook adjusts permissions on node-pty helper files.
AI rationale
Source inspection found no concrete attack behavior. The scanner's flagged login, process, and network signals correspond to user-invoked product functions or package-aligned setup.
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall hook changes permissions on node-pty spawn helpers, matching the package's terminal support.
- Port discovery examines local listeners and sends a localhost HTTP probe for previews.
- Login is user-invoked; its callback saves account tokens locally and uses them with the Supabase service.
- The host supplies account tokens only when connected to LinkShell's official gateway.
- The npm upgrade runs through the CLI upgrade command.
- Antigravity metadata names Google-hosted binaries and includes a pinned SHA-256 value.
Evidence against
- The scanner's command-output exfiltration signal is not supported by the inspected login flow.
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/drivers/acp/antigravity.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
Medium
Affected versions and remediation
This report applies to linkshell-cli@0.10.32.
See all versions of linkshell-cli for other recorded verdicts.
- Review the evidence and your use of linkshell-cli@0.10.32 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.