registry / @remcp/runtime / 0.2.173
@remcp/runtime@0.2.173
First-party ReMCP local device runtime: filesystem, terminal, computer-use, browser, diagnostics and document tools over MCP.
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe suspicious scanner signals resolve to ordinary local runtime capabilities and MCP dependencies. The package has no install hook, and inspected telemetry is limited to filtered metrics sent through the paired agent.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The runtime starts when its command is invoked; individual tools run when requested through MCP.
Impact
No confirmed malicious effect was identified in the inspected source.
Mechanism
It handles local file, screenshot, and system operations using caller-supplied tool arguments, while optional telemetry sends filtered usage metrics through the paired agent.
AI rationale
The suspicious scanner signals resolve to ordinary local runtime capabilities and MCP dependencies. The package has no install hook, and inspected telemetry is limited to filtered metrics sent through the paired agent.
Evidence
src/index.mjssrc/tools/files-write-edit.mjssrc/tools/files-screenshots.mjssrc/tools/system.mjssrc/telemetry.mjs
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 entry point is a local runtime command, with no install lifecycle hook in the manifest.
- File editing and screenshot capture are exposed as runtime tools that act on supplied arguments; the flagged process tool protects the runtime and its host agent from termination.
- Telemetry filters events to tool metrics and sends them through the paired runtime protocol; it does not define a third-party endpoint.
- The inspected runtime dependencies expose ordinary library and MCP server entry points and have no install lifecycle scripts.
- Bearer authentication verifies the supplied token and rejects it when its resource differs from the expected resource.
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
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.173.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.173 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.