linkshell-cli@0.10.36
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-aiThe inspected lifecycle behavior is limited to setting permissions on node-pty helpers. The flagged runtime behaviors are user-invoked or constrained to the package’s LinkShell authentication and remote development functions.
Decision evidence
public snapshot- The manifest registers a postinstall script that adjusts permissions on existing node-pty helper files.
- The login command opens LinkShell’s iTool login page with a loopback callback, checks the returned token with the configured Supabase service, and stores authentication locally.
- The host forwards an account token only when connected to LinkShell’s official gateway.
- Port preview connects to local loopback services and forwards their streams over the device connection, matching the package’s remote development purpose.
- Upgrading is a named CLI command that installs the latest linkshell-cli release when invoked.
- The Antigravity integration resolves an existing binary and returns no launch configuration when none is found.
Source & flagged code
9 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.36.
See all versions of linkshell-cli for other recorded verdicts.
- Review the evidence and your use of linkshell-cli@0.10.36 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.