linkshell-cli@0.5.42
Remote terminal bridge for Claude Code / Codex / Gemini / Copilot — control from your phone
AI Security Review
scanned 26d ago · by lpm-firewall-aiSource inspection shows a limited node-pty postinstall permission fix, package-owned hook cleanup, and user-invoked login and upgrade flows. The scanner's process and network signals correspond to those functions and do not establish malicious behavior.
Decision evidence
public snapshot- The install hook only locates node-pty spawn helpers and sets their executable permissions.
- The hook sweep targets existing LinkShell localhost hook entries in agent settings; it does not add hooks.
- The login flow accepts tokens through its local callback and uses them for authentication with the configured Supabase service.
- The upgrade command checks npm and installs a newer linkshell-cli release only when explicitly invoked.
- Agent subprocesses run using the selected command, arguments, working directory, and environment.
Source & flagged code
10 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage source references child process execution.
dist/cli/src/runtime/acp-relay.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to linkshell-cli@0.5.42.
See all versions of linkshell-cli for other recorded verdicts.
- Review the evidence and your use of linkshell-cli@0.5.42 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.