@remcp/runtime@0.2.69
First-party ReMCP local device runtime: filesystem, terminal, computer-use, browser, diagnostics and document tools over MCP.
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the inspected runtime behavior is consistent with local desktop and document tools. The browser endpoint is restricted to loopback, so the scanner signals do not establish a concrete attack.
Decision evidence
public snapshot- package.json defines start, check, and test scripts but no install lifecycle hook.
- src/extended/desktop-linux.mjs exposes screenshot capture as a runtime tool action.
- src/extended/documents.mjs resolves the requested document path before editing and restricts editing to DOCX files.
- src/extended/browser.mjs rejects browser CDP endpoints that are not loopback hosts.
Source & flagged code
5 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
src/extended/desktop-linux.mjsView on unpkg · L1046src/extended/desktop-linux.mjs exposes screenshot capture as a runtime tool action.
src/extended/desktop-linux.mjsView on unpkg · L1147Findings
Affected versions and remediation
This report applies to @remcp/runtime@0.2.69.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.69 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.