registry / @remcp/runtime / 0.2.117
@remcp/runtime@0.2.117
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-aiInspected entrypoint, flagged source files, and manifest behavior are consistent with the declared local ReMCP runtime. No install-time attack, hidden exfiltration, or concrete malicious chain was identified.
Static reason
One or more suspicious static signals were detected.
Trigger
A user or paired ReMCP agent starts the runtime and invokes its MCP tools.
Impact
No unauthorized mutation, credential theft, or malicious data transfer was established from the inspected source.
Mechanism
The runtime starts an MCP server; inspected desktop and document code provides bounded local operations and conditionally queries display state through D-Bus.
AI rationale
Inspected entrypoint, flagged source files, and manifest behavior are consistent with the declared local ReMCP runtime. No install-time attack, hidden exfiltration, or concrete malicious chain was identified.
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest has no install lifecycle hook; its start command launches the declared runtime entrypoint and dependencies support MCP and Linux desktop integration.
- The Linux display bridge loads its declared D-Bus dependency only in a Wayland session to query GNOME display state.
- Document handling imposes input size limits and opens files read-only with no-follow flags.
- The runtime starts an MCP server with tools for local device operations; inspected entrypoint behavior is consistent with its declared purpose.
- Telemetry sanitizes event details through a fixed field whitelist.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
5 flaggedsrc/extended/desktop-linux.mjsView file
1368package = @remcp/runtime; repositoryIdentity = remcp; dependency = @jellybrick/dbus-next
L1368: let dbus;
L1369: try { dbus = await import('@jellybrick/dbus-next'); } catch { return null; }
L1370: const bus = dbus.sessionBus();
High
Copied Package Dependency Bridge
Package metadata claims a different repository identity while copied source loads a runtime dependency bridge.
src/extended/desktop-linux.mjsView on unpkg · L13681366async function mutterDisplayInventory() {
if (!isWaylandSession()) return null;
let dbus;
try { dbus = await import('@jellybrick/dbus-next'); } catch { return null; }
const bus = dbus.sessionBus();
try {
const object = await bus.getProxyObject('o
Low
Suspicious Dependency Evidence
The Linux display bridge loads its declared D-Bus dependency only in a Wayland session to query GNOME display state.
src/extended/desktop-linux.mjsView on unpkg · L1366src/helpers/wayland-eis-helper.pyView file
Findings
2 High4 Medium6 Low
HighCopied Package Dependency Bridgesrc/extended/desktop-linux.mjs
HighSemantic Analysis Limitedsrc/extended/documents.mjs#virtual:normalized:round1
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helpersrc/helpers/wayland-eis-helper.py
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
LowSuspicious Dependency Evidencesrc/extended/desktop-linux.mjs
Affected versions and remediation
This report applies to @remcp/runtime@0.2.117.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.117 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.