@remcp/runtime@0.2.225
First-party ReMCP local device runtime: filesystem, terminal, computer-use, browser, diagnostics and document tools over MCP.
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe flagged dependency bridge serves the screenshot portal, and the package's runtime telemetry is disclosed, opt-out, and routed through the user's authenticated ReMCP account. No install-time contact or malicious data collection was identified.
Decision evidence
public snapshot- The manifest describes a first-party ReMCP local device runtime; its scripts are ordinary start, check, and test commands, with no install hook.
- The runtime discloses usage metrics, offers opt-out controls, and says metrics go to the user's own ReMCP account through its already-authenticated paired agent, with no third party or install ping.
- Telemetry events are limited to usage fields and exclude file paths, commands, arguments, and tool output; the payload includes runtime name, which defaults to the machine hostname.
- The screenshot portal loads the D-Bus dependency only when its screenshot capture function is called.
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 · L259Package 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.225.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.225 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.