@remcp/runtime@0.2.106
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 has no install lifecycle hook or runtime self-dependency, and inspected behavior aligns with a local device runtime. The scanner signals are explained by its loopback browser control, constrained telemetry fields, and document path validation.
Decision evidence
public snapshot- package.json has no install lifecycle hook; its scripts are start, check, and test.
- The required desktop Linux finding implements X11 window geometry lookup using a local helper.
- The required documents finding rejects absolute and parent-traversal archive entries.
- Browser CDP endpoint validation permits loopback hosts only.
- Telemetry event fields are restricted to bounded tool, timing, and outcome metadata.
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 · L1316The required desktop Linux finding implements X11 window geometry lookup using a local helper.
src/extended/desktop-linux.mjsView on unpkg · L51Findings
Affected versions and remediation
This report applies to @remcp/runtime@0.2.106.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.106 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.