@remcp/runtime@0.2.200
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 discloses opt-out telemetry routed through the paired agent, but its payload also includes a name that defaults to the host name. This is identifying telemetry not covered by the stated collection description, so it warrants a warning rather than a block.
Decision evidence
public snapshot- Runtime telemetry is enabled by default unless disabled by configuration.
- The telemetry payload includes runtimeConfig.name, which defaults to os.hostname() when no custom name is set.
- The telemetry sink sends the payload as an MCP notification through the paired agent.
- The CLI describes telemetry as including only tool names, timings and outcomes, but the payload also includes the runtime name.
- Telemetry is disclosed and has an opt-out.
- Telemetry fields exclude tool arguments, file paths, commands and output.
- The package declares no install lifecycle scripts; telemetry runs through the paired agent rather than a hard-coded third-party endpoint.
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.200.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.200 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.