excalidrop@0.2.11
Remote GitHub-backed Excalidraw canvas + MCP server — no local server, one-command setup
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe flagged command helper uses GitHub credentials for GitHub API operations, and the MCP relay flow is part of the documented canvas functionality. The relay receives the token for requested relay operations and uses it to verify access to the selected repository; no unrelated exfiltration or concealed behavior was found.
Decision evidence
public snapshot- The prepare and prepublishOnly scripts run the package build.
- The skill helper resolves a GitHub token and uses it for GitHub API requests to api.github.com.
- The MCP server sends the token to the shared relay only for relay RPC calls such as requested screenshots; the README documents the relay and says it forwards the token to GitHub per request.
- The relay uses the token to verify access to the requested GitHub repository.
- The local MCP server forwards a resolved GitHub token to the default shared relay for screenshot and viewport requests, creating a trust boundary users should know about.
Source & flagged code
9 flaggedPackage contains a high-severity secret pattern.
dist/frontend/assets/index-BNbEa8iL.jsView on unpkg · L41Google API key in dist/frontend/assets/index-BNbEa8iL.js
dist/frontend/assets/index-BNbEa8iL.jsView on unpkg · L41Findings
Affected versions and remediation
This report applies to excalidrop@0.2.11.
See all versions of excalidrop for other recorded verdicts.
- Review the evidence and your use of excalidrop@0.2.11 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.