registry / @remcp/runtime / 0.2.147
@remcp/runtime@0.2.147
First-party ReMCP local device runtime: filesystem, terminal, computer-use, browser, diagnostics and document tools over MCP.
AI Security Review
scanned 22d ago · by lpm-firewall-aiThe manifest has no install hook, and the inspected runtime behavior is exposed as caller-invoked local tools. Scanner-flagged display and document code serves those functions; no concrete attack behavior was found.
Static reason
One or more suspicious static signals were detected.
Trigger
The runtime starts through its executable; individual operations run when a caller invokes the corresponding tool.
Impact
No harmful effect was established; the inspected behavior matches the package’s local runtime function.
Mechanism
Local operations use caller-supplied tool arguments. Browser CDP control is restricted to a loopback endpoint, and telemetry is forwarded through the paired agent.
AI rationale
The manifest has no install hook, and the inspected runtime behavior is exposed as caller-invoked local tools. Scanner-flagged display and document code serves those functions; no concrete attack behavior was found.
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json lists start, check, and test scripts; it has no install lifecycle hook.
- The runtime exposes local tools through caller-invoked MCP handlers and says changes should occur only when the user asked for them.
- Browser control requires a loopback CDP endpoint.
- Telemetry is opt-out, limits event details, and travels through the paired agent; its payload also includes runtime metadata.
- The flagged Linux helper queries GNOME display state through D-Bus, while document operations resolve caller-provided paths.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
5 flaggedsrc/extended/desktop-linux.mjsView file
1378package = @remcp/runtime; repositoryIdentity = remcp; dependency = @jellybrick/dbus-next
L1378: let dbus;
L1379: try { dbus = await import('@jellybrick/dbus-next'); } catch { return null; }
L1380: 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 · L1378src/helpers/wayland-eis-helper.pyView file
•path = src/helpers/wayland-eis-helper.py
kind = build_helper
sizeBytes = 23624
magicHex = [redacted]
Medium
Ships Build Helper
Package ships non-JavaScript build or shell helper files.
src/helpers/wayland-eis-helper.pyView on unpkgsrc/extended/documents.mjs#virtual:normalized:round1
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
LowAi Review Evidencesrc/index.mjs
Affected versions and remediation
This report applies to @remcp/runtime@0.2.147.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.147 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.