@remcp/runtime@0.2.193
First-party ReMCP local device runtime: filesystem, terminal, computer-use, browser, diagnostics and document tools over MCP.
AI Security Review
scanned 7d ago · by lpm-firewall-aiSource inspection found no install-time execution or concrete malicious behavior. The flagged runtime operations are consistent with the package’s local device tools, and the reviewed metrics path is constrained and uses the paired agent.
Decision evidence
public snapshot- package.json declares no install lifecycle hooks; its runtime starts through the published command and uses two runtime dependencies.
- The MCP dependency excerpt handles one request through its server transport, while its subscription listener forwards only events accepted by the requested filter.
- The DBus dependency is used by the screenshot portal integration for desktop capture; its manifest lists ordinary XML parsing dependencies and no install scripts.
- Screenshot commands are invoked for capture, and process listing runs the platform’s process-listing utility when that tool is requested.
- Runtime metrics are sent through the paired MCP agent, and event details are filtered through a limited field whitelist.
Source & flagged code
5 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
src/screenshot-portal.mjsView on unpkg · L249Package ships non-JavaScript build or shell helper files.
src/helpers/wayland_eis_sender.pyView on unpkgFindings
Affected versions and remediation
This report applies to @remcp/runtime@0.2.193.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.193 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.