registry / linkshell-cli / 0.10.65
linkshell-cli@0.10.65
⚠ 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 11d ago · by lpm-firewall-aiThe inspected lifecycle hook and login flow show ordinary package behavior, and the scanner hints alone do not establish an attack. The selected node-pty dependency remained unresolved, so its code and install behavior could not be verified; manual review is warranted.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Dependency installation or use of the host terminal feature; the unresolved dependency's behavior could not be determined.
Impact
Unknown; the available source does not establish an attack or its effect.
Mechanism
The package declares and imports node-pty, but its source was unavailable in the supplied dependency snapshot.
AI rationale
The inspected lifecycle hook and login flow show ordinary package behavior, and the scanner hints alone do not establish an attack. The selected node-pty dependency remained unresolved, so its code and install behavior could not be verified; manual review is warranted.
Evidence
package.jsondist/host/src/terminals.js
Decision evidence
public snapshotAI called this Manual Review at 72.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The postinstall hook runs a script that only makes existing platform-specific node-pty helper files executable.
- The login flow binds its callback to loopback, validates the returned access token with the configured Supabase service, and stores credentials locally.
- The host imports node-pty for its terminal feature, but the supplied snapshot leaves that selected registry dependency unresolved, so its code and install behavior could not be verified.
Evidence against
- The inspected postinstall source contains no network request; it changes helper-file permissions.
- The inspected login path validates tokens with the configured Supabase service and saves them to the local auth file.
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/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
Affected versions and remediation
This report applies to linkshell-cli@0.10.65.
See all versions of linkshell-cli for other recorded verdicts.
- Review the evidence and your use of linkshell-cli@0.10.65 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.