@remcp/runtime@0.2.116
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-aiSource inspection found no install lifecycle hook or concrete malicious behavior. The scanner's network and execution signals correspond to the local runtime's browser and desktop features, with the browser endpoint restricted to loopback.
Decision evidence
public snapshot- package.json defines no preinstall, install, or postinstall hook; its scripts are start, check, and test.
- The desktop Linux launch helper passes the selected app and arguments to the launcher as an explicit runtime operation.
- Document reads resolve the requested path through the runtime safe-path resolver.
- Browser debugging endpoints require loopback hosts, limiting this network access to a local browser endpoint.
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 Linux launch helper passes the selected app and arguments to the launcher as an explicit runtime operation.
src/extended/desktop-linux.mjsView on unpkg · L1622Findings
Affected versions and remediation
This report applies to @remcp/runtime@0.2.116.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.116 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.