registry / @remcp/runtime / 0.2.49

@remcp/runtime@0.2.49

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

The flagged behavior is consistent with the package's declared local device runtime: it has no install lifecycle hook, and the inspected network access is restricted to loopback. No concrete malicious behavior was established.

Static reason

One or more suspicious static signals were detected.

Trigger

The runtime starts when invoked through its command-line entrypoint; individual device operations are exposed as MCP tools.

Impact

No concrete malicious effect was established from the inspected source.

Mechanism

The inspected code loads its declared desktop dependency, handles documents with archive path checks, and limits browser requests to loopback endpoints.

AI rationale

Network endpoints1

127.0.0.1:9222

Decision evidence

public snapshot

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

Evidence for AI clean decision

package.json defines a start script but no preinstall, install, or postinstall hook; its runtime dependencies support the declared MCP and desktop runtime.
The flagged desktop module dynamically loads its declared D-Bus dependency for Linux desktop integration.
Document archive handling rejects absolute and parent-traversal paths.
Browser DevTools requests require a loopback host and HTTP or HTTPS.
The entrypoint describes local tools and says side effects should occur only when the user asked for them.
Telemetry limits event fields and routes them through the paired ReMCP agent.

Evidence against

Behavioral surface

Source

ChildProcessCryptoEnvironmentVarsFilesystemNetworkWebSocket

Supply chain

HighEntropyStringsUrlStrings

ManifestNo manifest risk signals triggered.

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

Source & flagged code

5 flagged

src/extended/desktop-linux.mjsView file

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

1029try { dbus = await import('@jellybrick/dbus-next'); } catch { return null; } const bus = dbus.sessionBus(); try { const object = await bus.getProxyObjec

Low

Suspicious Dependency Evidence

The flagged desktop module dynamically loads its declared D-Bus dependency for Linux desktop integration.

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

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.49.

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

Review the evidence and your use of @remcp/runtime@0.2.49 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:34.987Z (UTC).

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

registry / @remcp/runtime / 0.2.49

@remcp/runtime@0.2.49

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 runtime starts when invoked through its command-line entrypoint; individual device operations are exposed as MCP tools.

Impact

No concrete malicious effect was established from the inspected source.

Mechanism

The inspected code loads its declared desktop dependency, handles documents with archive path checks, and limits browser requests to loopback endpoints.

AI rationale

Network endpoints1

127.0.0.1:9222

Decision evidence

public snapshot

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

Evidence for AI clean decision

package.json defines a start script but no preinstall, install, or postinstall hook; its runtime dependencies support the declared MCP and desktop runtime.
The flagged desktop module dynamically loads its declared D-Bus dependency for Linux desktop integration.
Document archive handling rejects absolute and parent-traversal paths.
Browser DevTools requests require a loopback host and HTTP or HTTPS.
The entrypoint describes local tools and says side effects should occur only when the user asked for them.
Telemetry limits event fields and routes them through the paired ReMCP agent.

Evidence against

Behavioral surface

Source

ChildProcessCryptoEnvironmentVarsFilesystemNetworkWebSocket

Supply chain

HighEntropyStringsUrlStrings

ManifestNo manifest risk signals triggered.

scanned 32 file(s), 548 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 · L1028

1029try { dbus = await import('@jellybrick/dbus-next'); } catch { return null; } const bus = dbus.sessionBus(); try { const object = await bus.getProxyObjec

Low

Suspicious Dependency Evidence

The flagged desktop module dynamically loads its declared D-Bus dependency for Linux desktop integration.

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

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.49.

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

Review the evidence and your use of @remcp/runtime@0.2.49 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:34.987Z (UTC).

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