@remcp/runtime@0.2.63
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 hook or concrete malicious behavior; the flagged dependency bridge and network use match the runtime's local desktop and browser functions. The browser endpoint is loopback-only, archive paths are checked, and telemetry fields are whitelisted.
Decision evidence
public snapshot- package.json exposes a normal runtime CLI entrypoint and has no install lifecycle hook.
- The Linux display code conditionally imports the declared D-Bus dependency only for Wayland display inventory.
- Document archive handling rejects absolute paths and parent-directory traversal.
- Browser CDP requests are restricted to loopback hosts.
- Telemetry code whitelists event fields and excludes file paths, commands, arguments, and output.
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 · L1046The Linux display code conditionally imports the declared D-Bus dependency only for Wayland display inventory.
src/extended/desktop-linux.mjsView on unpkg · L1044Findings
Affected versions and remediation
This report applies to @remcp/runtime@0.2.63.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.63 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.