registry / @remcp/runtime / 0.2.194
@remcp/runtime@0.2.194
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 flagged files implement desktop capture and system information or process tools consistent with the package’s purpose. No install-time contact or concealed unrelated behavior was found; telemetry is limited to usage metadata and can be disabled.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The runtime starts when invoked; local actions occur when its MCP tools are called.
Impact
No malicious impact identified. Local tools can perform consequential actions when requested, and telemetry is opt-out.
Mechanism
It serves MCP over stdio, uses D-Bus for requested desktop capture, and forwards whitelisted usage telemetry through an MCP notification.
AI rationale
The flagged files implement desktop capture and system information or process tools consistent with the package’s purpose. No install-time contact or concealed unrelated behavior was found; telemetry is limited to usage metadata and can be disabled.
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package defines start, check and test scripts, with no install lifecycle hooks.
- Telemetry restricts event fields to tool names, timings, outcomes and coarse error classes; it excludes paths, commands, arguments and output.
- Telemetry is forwarded as an MCP notification by the runtime server.
- Screenshot portal code loads D-Bus when capture is requested, matching the package’s desktop capture purpose.
- Process termination requires a supplied PID and refuses to terminate protected or runtime-related processes.
Evidence against
- Telemetry is enabled by default unless disabled, and includes runtime and tool-use metadata.
- The runtime exposes powerful local capabilities, including process termination, when invoked through its tools.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkWebSocket
HighEntropyStringsUrlStrings
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.194.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.194 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.