linkshell-cli@0.10.67
Follow, 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-aiSource inspection resolved the flagged lifecycle, login, process, and network behavior as package-aligned setup or user-invoked CLI functionality. The reviewed login path sends its access token to the configured Supabase service and saves tokens locally; no unrelated credential recipient or other concrete attack was found.
Decision evidence
public snapshot- package.json runs a postinstall script that sets executable permissions on node-pty spawn-helper files; node-pty's install hooks check prebuilt binaries and prepare native build files.
- Login sends the access token to the configured Supabase service for account verification, then saves the returned tokens locally.
- Host gateway selection uses an environment or saved setting, otherwise the LinkShell gateway for logged-in users; port inspection uses execFile for local listener discovery.
- Upgrade checks the npm registry and invokes npm or Homebrew only when the user runs the upgrade command.
- Inspected dependency manifests and sources describe CLI parsing, terminal process creation, QR display, and native terminal build setup.
Source & flagged code
8 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/host/src/ports.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to linkshell-cli@0.10.67.
See all versions of linkshell-cli for other recorded verdicts.
- Review the evidence and your use of linkshell-cli@0.10.67 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.