Markdown Editor With Chat

Lightweight markdown editor with optional OpenClaw gateway chat. Filesystem-based, no database required.

This package appears to be what it says: a local markdown editor that serves files from a directory and can optionally proxy chat requests to an OpenClaw gateway. Before installing/running, consider the following: - Set MARKDOWN_DIR to a directory you control and do not point it at system or secret-bearing directories (e.g., /, /root, ~/.ssh). The server will read and write files under that directory. - If you enable chat, the server will make outbound requests to OPENCLAW_GATEWAY_URL using OPENCLAW_GATEWAY_TOKEN; the token is sent only by the server (not exposed to the browser) but you should ensure the gateway endpoint is trusted. - The server enforces a localhost/private-host binding by default, but verify you run it on a safe host and do not deliberately expose it to the public internet. - The code uses the Node global fetch API — run with a modern Node.js (Node 18+). If you need higher assurance, you can review the complete scripts/server.mjs and index.html (both included) locally before running; otherwise running it in an isolated environment (e.g., a throwaway VM or container) is a reasonable precaution.

Type: OpenClaw Skill Name: markdown-editor-with-chat Version: 1.1.2 The skill is classified as suspicious due to a client-side Cross-Site Scripting (XSS) vulnerability in the custom markdown renderer within `scripts/index.html`. The `renderMarkdown` function directly embeds user-controlled `href` values from markdown links into `<a>` tags without sanitizing the protocol, allowing `javascript:` URLs to execute arbitrary code in the user's browser. Additionally, the chat feature presents a prompt injection risk against the OpenClaw gateway AI, as it sends the current markdown file content as context, which could be manipulated by a malicious user to influence AI responses. While server-side security measures are robust (e.g., path traversal protection, host binding to localhost/private IPs), the client-side XSS is a significant vulnerability.