@remcp/runtime@0.2.138
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-aiSource inspection found no concrete attack behavior. The scanner signals are consistent with package-aligned local runtime capabilities and do not support a warning or block.
Decision evidence
public snapshot- package.json defines no install lifecycle hook; its scripts are start, check, and test.
- The Linux desktop module dynamically imports the declared D-Bus dependency for desktop integration.
- Document reads use read-only, no-follow file flags.
- Telemetry restricts event fields to bounded, coarse values.
- Browser control defaults to a loopback DevTools endpoint.
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 dynamically imports the declared D-Bus dependency for desktop integration.
src/extended/desktop-linux.mjsView on unpkg · L1369Findings
Affected versions and remediation
This report applies to @remcp/runtime@0.2.138.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.138 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.