@remcp/runtime@0.2.100
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 inspected source supports an ordinary local MCP runtime: there are no install hooks, the flagged dependency is declared directly, and archive paths are validated. The scanner signals do not establish malicious behavior.
Decision evidence
public snapshot- package.json contains no install lifecycle hook and declares @jellybrick/dbus-next as a direct dependency.
- The flagged Linux module dynamically imports that declared dependency only for Wayland display inventory.
- The documents module rejects absolute and parent-traversal archive paths.
- The runtime starts its MCP server from the declared command-line entrypoint.
- Telemetry limits event fields to tool names, timing, outcomes, and coarse error classes.
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 · L1205The flagged Linux module dynamically imports that declared dependency only for Wayland display inventory.
src/extended/desktop-linux.mjsView on unpkg · L1203Findings
Affected versions and remediation
This report applies to @remcp/runtime@0.2.100.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.100 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.