registry / @remcp/runtime / 0.2.198
@remcp/runtime@0.2.198
First-party ReMCP local device runtime: filesystem, terminal, computer-use, browser, diagnostics and document tools over MCP.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package’s runtime behavior matches its stated local-device tooling purpose. Its default-on runtime metrics are disclosed, limited to usage fields, routed through the paired ReMCP agent, and can be disabled.
Static reason
One or more suspicious static signals were detected.
Trigger
Telemetry can be emitted while the runtime is running, and screen capture occurs when its tool is invoked.
Impact
No unauthorized collection, unrelated network contact, or other attack behavior was found in the reviewed paths.
Mechanism
Metrics are filtered and sent through the paired-agent MCP channel; screenshots use the local desktop portal and D-Bus dependency.
AI rationale
The package’s runtime behavior matches its stated local-device tooling purpose. Its default-on runtime metrics are disclosed, limited to usage fields, routed through the paired ReMCP agent, 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 runs as a local MCP runtime via its `remcp-runtime` binary and declares no install lifecycle scripts.
- Runtime help discloses opt-out usage metrics, says they go through the paired ReMCP agent to the user's account, and provides ways to disable them.
- Telemetry code limits event fields to tool names, timings, outcomes, and coarse error classes; it excludes paths, commands, arguments, and tool output.
- Telemetry is sent through the MCP server notification sink, with runtime version and platform details.
- The screenshot module lazily imports the declared D-Bus dependency for portal-based screen capture.
Evidence against
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
2 High4 Medium6 Low
HighCopied Package Dependency Bridgesrc/screenshot-portal.mjs
HighSemantic Analysis Limitedsrc/tools/files-screenshots.mjs#virtual:normalized:round1
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
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to @remcp/runtime@0.2.198.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.198 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.