@remcp/runtime@0.2.98
First-party ReMCP local device runtime: filesystem, terminal, computer-use, browser, diagnostics and document tools over MCP.
AI Security Review
scanned 27d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the inspected source shows runtime startup, conditional display integration, and archive path validation. The scanner signals do not establish malicious behavior.
Decision evidence
public snapshot- package.json has no install lifecycle hook; its start script launches the declared runtime entrypoint.
- The Linux display bridge imports D-Bus only during a Wayland display inventory call.
- Document archive handling rejects absolute paths and parent-directory entries.
- The entrypoint starts an MCP server when the runtime is invoked.
- No concrete malicious behavior was identified in the inspected source.
Source & flagged code
5 flaggedPackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
src/extended/desktop-linux.mjsView on unpkg · L1204The Linux display bridge imports D-Bus only during a Wayland display inventory call.
src/extended/desktop-linux.mjsView on unpkg · L1202Findings
Affected versions and remediation
This report applies to @remcp/runtime@0.2.98.
See all versions of @remcp/runtime for other recorded verdicts.
- Review the evidence and your use of @remcp/runtime@0.2.98 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.