linkshell-cli@0.10.93
Follow, steer and approve the coding agents on your computer (Claude Code, Codex, Gemini, Copilot and more) from your phone
AI Security Review
scanned 4h ago · by lpm-firewall-aiThe install hook only fixes executable permissions on node-pty helpers. The flagged process execution and network activity supports explicit upgrade, account sign-in, and local agent integration; no malicious data flow or unauthorized action was found.
Decision evidence
public snapshot- The postinstall hook locates node-pty's platform helpers and changes their executable permissions.
- The upgrade command is registered as a user-run CLI command; it checks the npm registry and upgrades LinkShell through npm or Homebrew.
- Password sign-in is an explicit command flow, and the package documents its LinkShell gateway and token proxy as part of its account and remote-access features.
- Antigravity integration reads a local process token to call the running local language server.
- The package has a postinstall hook, but its code only adjusts node-pty helper permissions.
- Sign-in tokens pass through the LinkShell vendor proxy before direct Supabase fallback; the inspected flow is tied to user-initiated login or token refresh.
Source & flagged code
21 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.93.
See all versions of linkshell-cli for other recorded verdicts.
- Review the evidence and your use of linkshell-cli@0.10.93 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.