registry / @remcp/runtime / 0.2.189
@remcp/runtime@0.2.189
First-party ReMCP local device runtime: filesystem, terminal, computer-use, browser, diagnostics and document tools over MCP.
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe suspicious indicators resolve to advertised local runtime functions and ordinary MCP dependencies. The inspected sources show no install-time execution, unrelated recipient, or other concrete attack behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The runtime starts when its executable is launched; its tools operate when called by the connected client.
Impact
No concrete unauthorized change, credential transfer, or unrelated data disclosure was established.
Mechanism
Inspected file, process, screenshot, and telemetry operations use caller-provided inputs or the paired runtime channel.
AI rationale
The suspicious indicators resolve to advertised local runtime functions and ordinary MCP dependencies. The inspected sources show no install-time execution, unrelated recipient, or other concrete attack behavior.
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json runs a local MCP runtime and has no install lifecycle hook; the dependency manifests show ordinary development scripts.
- The bundled server routes filtered protocol events, and its stdio transport reads from standard input and writes to standard output.
- Screenshot capture uses a requested or temporary directory and calls the local desktop screenshot portal.
- File writes resolve the caller-supplied path; process termination validates the requested process and protects the runtime and host agent.
- Telemetry fields are limited to tool names, timings, outcomes, and coarse error classes, and are sent through the paired runtime channel with a configuration opt-out.
Evidence against
- The flagged local file, process, screenshot, and network primitives match the advertised device-runtime functions; inspection found no concrete attack behavior.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkWebSocket
Source & flagged code
5 flaggedsrc/screenshot-portal.mjsView file
249package = @remcp/runtime; repositoryIdentity = remcp; dependency = @jellybrick/dbus-next
L249: timeoutMs = DEFAULT_TIMEOUT_MS,
L250: loadDbus = () => import('@jellybrick/dbus-next'),
L251: } = {}) {
High
Copied Package Dependency Bridge
Package metadata claims a different repository identity while copied source loads a runtime dependency bridge.
src/screenshot-portal.mjsView on unpkg · L249src/helpers/wayland_eis_sender.pyView file
•path = src/helpers/wayland_eis_sender.py
kind = build_helper
sizeBytes = 15744
magicHex = [redacted]
Medium
Ships Build Helper
Package ships non-JavaScript build or shell helper files.
src/helpers/wayland_eis_sender.pyView on unpkgsrc/tools/files-screenshots.mjs#virtual:normalized:round1View file
Findings
3 High4 Medium5 Low
HighCopied Package Dependency Bridgesrc/screenshot-portal.mjs
HighSemantic Analysis Limitedsrc/tools/files-screenshots.mjs#virtual:normalized:round1
HighPrevious Version Dangerous Deltasrc/tools/system.mjs
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helpersrc/helpers/wayland_eis_sender.py
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to @remcp/runtime@0.2.189.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.189 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.