@remcp/runtime@0.2.118
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 package has no install lifecycle hook, and inspected source shows ordinary, user-invoked local runtime functionality with bounded document reads and loopback-restricted browser control. The scanner signals do not establish malicious behavior.
Decision evidence
public snapshot- package.json defines no install lifecycle hook; its scripts are explicit start, check, and test commands.
- The desktop D-Bus bridge is imported only for Wayland display inventory and returns unavailable if the optional dependency cannot load.
- Document handling sets size limits and opens files read-only with no-follow flags.
- The CLI describes a local MCP runtime started by the ReMCP device agent, with local device tools.
- Browser CDP endpoints are restricted to loopback hosts.
- Browser CDP requests use the validated endpoint and reject redirects.
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 desktop D-Bus bridge is imported only for Wayland display inventory and returns unavailable if the optional dependency cannot load.
src/extended/desktop-linux.mjsView on unpkg · L1366Findings
Affected versions and remediation
This report applies to @remcp/runtime@0.2.118.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.118 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.