@remcp/runtime@0.2.113
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-aiThe manifest contains no install hook, and inspected flagged code supports the package’s local runtime functions. Telemetry is opt-out, but the inspected code limits event fields and sends through the paired MCP connection; no concrete attack behavior was found.
Decision evidence
public snapshot- package.json has no install lifecycle hook and starts the declared CLI entry point.
- The Linux desktop module loads its declared D-Bus dependency only for Wayland display inventory.
- Document handling opens a caller-selected path as a regular file.
- Telemetry is sent through the MCP server notification sink, and its event fields are whitelisted.
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 · L1368The Linux desktop module loads its declared D-Bus dependency only for Wayland display inventory.
src/extended/desktop-linux.mjsView on unpkg · L1366Findings
Affected versions and remediation
This report applies to @remcp/runtime@0.2.113.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.113 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.