Prepare Loadpath for public release - #28
Conversation
The UI HTTP API (settings, filesystem, review, PR comments) now rejects non-loopback Origin/Host so a tunneled MCP server cannot be CSRF'd from another site. MCP transport checks Host against loopback or --public-url. The composite action passes inputs through env vars and drops extra-args shell interpolation. Co-authored-by: zord.lack.net <zord.lack.net@gmail.com>
Lead with what Loadpath does and does not do, then clone-to-run setup for CLI, UI, Action, MCP, and desktop. Add a Code of Conduct, issue templates, Dependabot, and a security policy that matches the loopback API model. Co-authored-by: zord.lack.net <zord.lack.net@gmail.com>
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Free Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Note 🎁 Summarized by CodeRabbit FreeYour organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login. Comment |
Why
The repo is about to be public. The README buried setup under screenshots, and the local HTTP API was only partially loopback-gated — a page on another origin could hit settings, the filesystem browser, review, and PR comments while
loadpath servewas running.What changed
Security
/api/*except/api/healthrejects non-loopbackOrigin/Host/mcp(and OAuth token routes) reject unexpectedHostheaders;--public-urlhost is allowedextra-argsshell interpolation is gonecontents: readDocs / community
After merge (GitHub settings)
These cannot be set from the repo files:
django,react,code-review,architecture,mcpTests
/apiis 403,/api/healthstays 200, MCPHost: evil.exampleis 421