linkshell-cli@0.10.82
Follow, steer and approve the coding agents on your computer (Claude Code, Codex, Gemini, Copilot and more) from your phone
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe install hook only fixes permissions on node-pty helpers. The network and process behavior is tied to explicit upgrade or LinkShell sign-in flows, and no attack behavior was found.
Decision evidence
public snapshot- The postinstall hook only locates node-pty spawn-helper files and sets their executable permissions.
- The upgrade command fetches the package version from the npm registry; its process execution is part of the explicit upgrade flow.
- The sign-in proxy handles LinkShell login grants, with direct fallback to the package's configured Supabase service.
- The CLI entry point registers commands and does not run an upgrade at import time.
- The package has a postinstall hook that changes file permissions.
- The upgrade command uses child processes and makes an outbound request when invoked.
- The sign-in flow sends login grants to itool.tech before falling back to Supabase.
Source & flagged code
20 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.82.
See all versions of linkshell-cli for other recorded verdicts.
- Review the evidence and your use of linkshell-cli@0.10.82 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.