@remcp/runtime@0.2.104
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 runtime with no install-time execution, loopback-only browser discovery, and opt-in filtered telemetry through the paired agent. The scanner hints do not establish malicious behavior.
Decision evidence
public snapshot- The manifest defines a CLI entrypoint and no install lifecycle hook or runtime self-dependency.
- The flagged Linux desktop module imports platform and filesystem utilities; its inspected excerpt shows no dependency bridge or active attack behavior.
- The flagged document module imports filesystem operations and safe-path handling; its inspected excerpt shows no attack behavior.
- Browser discovery restricts configured endpoints to loopback before sending requests.
- Telemetry is opt-in, and event details are filtered through a whitelist before buffering.
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 · L1291The flagged Linux desktop module imports platform and filesystem utilities; its inspected excerpt shows no dependency bridge or active attack behavior.
src/extended/desktop-linux.mjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @remcp/runtime@0.2.104.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.104 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.