@remcp/runtime@0.2.122
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 install-time hook, self-dependency chain, or concrete malicious behavior in the flagged files. The static signals are consistent with the package's local device runtime functionality.
Decision evidence
public snapshot- package.json defines start, check, and test scripts but no install lifecycle hook or runtime self-dependency.
- The package exposes a local MCP runtime whose entrypoint advertises core and extended tools.
- The flagged desktop and document modules import filesystem and platform helpers for device and document functions; inspected source searches found no network, process execution, or dynamic evaluation in those files.
- Browser control defaults to the local CDP endpoint and limits browser URL protocols.
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 flagged desktop and document modules import filesystem and platform helpers for device and document functions; inspected source searches found no network, process execution, or dynamic evaluation in those files.
src/extended/desktop-linux.mjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @remcp/runtime@0.2.122.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.122 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.