@remcp/runtime@0.2.207
First-party ReMCP local device runtime: filesystem, terminal, computer-use, browser, diagnostics and document tools over MCP.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package's runtime telemetry is disclosed, opt-out, and limited to tool names, timings, outcomes, and coarse error classes sent through the paired agent. The screenshot and process capabilities serve the advertised local device tools, and the package declares no install lifecycle hooks.
Decision evidence
public snapshot- The package exposes a runtime CLI and its scripts define no preinstall, install, or postinstall hook.
- Runtime usage metrics are disclosed as opt-out and sent through the already-authenticated paired agent to the user's ReMCP account.
- Telemetry fields are whitelisted and exclude file paths, commands, tool arguments, and tool output.
- Screenshot capture is an explicit tool operation; the portal code requests a local screenshot through the desktop portal.
- Runtime telemetry is enabled by default, but the package discloses it and provides opt-out controls.
- The package uses process and filesystem APIs for its stated local device tools.
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.207.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.207 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.