registry / @remcp/runtime / 0.2.68

@remcp/runtime@0.2.68

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-ai

Source inspection found package-aligned local runtime behavior, with a loopback restriction on browser CDP and bounded telemetry fields. The scanner’s bridge hint corresponds to the declared D-Bus dependency used for Linux desktop integration; the package has no lifecycle hooks in its manifest.

Static reason

One or more suspicious static signals were detected.

Trigger

The CLI starts the MCP runtime; individual desktop, browser, and document operations are invoked as tools.

Impact

No confirmed attack surface was established in the inspected code.

Mechanism

The inspected browser client restricts its CDP endpoint to loopback, document reads use a safe-path resolver, and telemetry is forwarded through the paired agent with limited event fields.

AI rationale

Decision evidence

public snapshot

AI called this Clean at 91.0% confidence as Benign with low false-positive risk.

Evidence for AI clean decision

package.json identifies this as a first-party ReMCP local device runtime with a CLI entry point and no lifecycle hooks.
Linux desktop integration dynamically imports the declared D-Bus dependency to access Mutter’s display interface.
Document reads resolve the requested path through the runtime’s safe-path helper before reading.
Browser CDP requests reject non-loopback endpoints, including when the endpoint comes from configuration.
Telemetry fields are limited to tool names, timings, outcomes, and coarse error classes; the entry point forwards telemetry through the paired MCP agent.

Evidence against

Behavioral surface

Source

ChildProcessCryptoEnvironmentVarsFilesystemNetworkWebSocket

Supply chain

HighEntropyStringsUrlStrings

ManifestNo manifest risk signals triggered.

scanned 32 file(s), 567 KB of source, external domains: 127.0.0.1

Source & flagged code

5 flagged

src/extended/desktop-linux.mjsView file

1046package = @remcp/runtime; repositoryIdentity = remcp; dependency = @jellybrick/dbus-next L1046: let dbus; L1047: try { dbus = await import('@jellybrick/dbus-next'); } catch { return null; } L1048: 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 · L1046

1047@jellybrick/dbus-next'); } catch { return null; } const bus = dbus.sessionBus(); try { const object = await bus.getProxyObject('org.gnome.Mutter.Di

Low

Suspicious Dependency Evidence

Linux desktop integration dynamically imports the declared D-Bus dependency to access Mutter’s display interface.

src/extended/desktop-linux.mjsView on unpkg · L1047

src/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.68.

See all versions of @remcp/runtime for other recorded verdicts.

Review the evidence and your use of @remcp/runtime@0.2.68 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: 2026-10-09 05:59:49.747Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.

registry / @remcp/runtime / 0.2.68

@remcp/runtime@0.2.68

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-ai

Static reason

One or more suspicious static signals were detected.

Trigger

The CLI starts the MCP runtime; individual desktop, browser, and document operations are invoked as tools.

Impact

No confirmed attack surface was established in the inspected code.

Mechanism

The inspected browser client restricts its CDP endpoint to loopback, document reads use a safe-path resolver, and telemetry is forwarded through the paired agent with limited event fields.

AI rationale

Decision evidence

public snapshot

AI called this Clean at 91.0% confidence as Benign with low false-positive risk.

Evidence for AI clean decision

package.json identifies this as a first-party ReMCP local device runtime with a CLI entry point and no lifecycle hooks.
Linux desktop integration dynamically imports the declared D-Bus dependency to access Mutter’s display interface.
Document reads resolve the requested path through the runtime’s safe-path helper before reading.
Browser CDP requests reject non-loopback endpoints, including when the endpoint comes from configuration.
Telemetry fields are limited to tool names, timings, outcomes, and coarse error classes; the entry point forwards telemetry through the paired MCP agent.

Evidence against

Behavioral surface

Source

ChildProcessCryptoEnvironmentVarsFilesystemNetworkWebSocket

Supply chain

HighEntropyStringsUrlStrings

ManifestNo manifest risk signals triggered.

scanned 32 file(s), 567 KB of source, external domains: 127.0.0.1

Source & flagged code

5 flagged

src/extended/desktop-linux.mjsView file

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 · L1046

1047@jellybrick/dbus-next'); } catch { return null; } const bus = dbus.sessionBus(); try { const object = await bus.getProxyObject('org.gnome.Mutter.Di

Low

Suspicious Dependency Evidence

Linux desktop integration dynamically imports the declared D-Bus dependency to access Mutter’s display interface.

src/extended/desktop-linux.mjsView on unpkg · L1047

src/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.68.

See all versions of @remcp/runtime for other recorded verdicts.

Review the evidence and your use of @remcp/runtime@0.2.68 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: 2026-10-09 05:59:49.747Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.