linkshell-cli@0.10.73
Follow, steer and approve the coding agents on your computer (Claude Code, Codex, Gemini, Copilot and more) from your phone
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe install hook only fixes permissions for node-pty helper binaries. The flagged network and process activity belongs to explicit upgrade or login flows, and the inspected credential use stays with LinkShell’s configured Supabase service.
Decision evidence
public snapshot- The postinstall hook resolves node-pty’s spawn-helper files and makes existing helpers executable.
- The CLI invokes the upgrade flow only through the explicit `linkshell upgrade` command.
- The upgrade check requests the latest package version from npm’s registry.
- Login receives tokens through its callback and sends the access token to the configured Supabase service to validate the account.
- Login saves the returned credentials locally with file mode 0600.
- The package has a postinstall script and uses child-process execution and network requests in some command flows.
- The CLI handles access and refresh tokens during login, but the inspected flow sends the access token to its configured Supabase service and stores the credentials locally.
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.73.
See all versions of linkshell-cli for other recorded verdicts.
- Review the evidence and your use of linkshell-cli@0.10.73 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.