@remcp/runtime@0.2.120
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-aiInspected source supports a local device runtime with no install lifecycle hook. The flagged network and environment use is consistent with its paired-agent telemetry and configurable local runtime behavior; no concrete attack surface was found.
Decision evidence
public snapshot- package.json defines start, check, and test scripts but no install lifecycle hook.
- The desktop code uses the user-session portal for Wayland input.
- Document reads require a regular file and enforce a size limit.
- Telemetry is sent through the runtime server notification sink and its event fields are sanitized.
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 · L1368The desktop code uses the user-session portal for Wayland input.
src/extended/desktop-linux.mjsView on unpkg · L1326Findings
Affected versions and remediation
This report applies to @remcp/runtime@0.2.120.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.120 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.