@lsproxy/cli
Standalone refactor CLI driving any LSP server: project-wide rename, file-move with importer updates, and move-symbol
This report shows the evidence for @lsproxy/cli@0.11.4. 2 of 8 known versions are blocked or flagged. The newest version, 1.1.2, is flagged. See all versions.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiAlthough the CLI runtime behavior is largely aligned with LSP/refactoring functionality, the unguarded install-time write into ~/.claude/skills matches the policy for unconsented lifecycle mutation of a foreign AI-agent control surface. No additional exfiltration or remote payload behavior is needed for this block decision.
Decision evidence
public snapshot- package.json defines postinstall: node ./skillit-postinstall.cjs
- skillit-postinstall.cjs runs at install time and copies packaged skills into os.homedir()/.claude/skills
- skills/lsproxy-cli/SKILL.md is package-supplied Claude skill content for invoking lsproxy commands
- skillit-postinstall.cjs mutates packaged .md files before copying them
- No credential harvesting or exfiltration endpoints found in inspected source
- dist/connect.js daemon behavior is user-invoked CLI/proxy functionality
- dist/session.js child_process spawn runs user-selected language server commands during CLI use
- Config adapter writes are exposed through explicit lsproxy config commands
Source & flagged code
4 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time source drops package-supplied AI-agent/MCP control files or instructions.
skillit-postinstall.cjsView on unpkg · L26Findings
Affected versions and remediation
This report applies to @lsproxy/cli@0.11.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing @lsproxy/cli@0.11.4. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.