excalidrop@0.2.12
Remote GitHub-backed Excalidraw canvas + MCP server — no local server, one-command setup
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe reviewed credential flow supports the package’s stated GitHub-backed canvas and relay features. Although a GitHub token is sent to the package’s default relay for RPC authorization, the reviewed source ties those requests to canvas operations and shows repository access checks rather than unrelated collection.
Decision evidence
public snapshot- The manifest’s prepare and prepublishOnly scripts run builds; it declares no install or postinstall hook.
- The MCP server gets GitHub credentials from GITHUB_TOKEN, gh auth, or its stored device-flow token.
- The relay receives the GitHub bearer token for RPC requests, including repo and method in the request URL.
- The screenshot helper calls the relay for a screenshot operation; the request is tied to an MCP tool call.
- The relay checks repository access with the token and documents that tokens are not persisted; its cache key hashes the token.
- The README documents the default relay URL and the GitHub token setting.
Source & flagged code
9 flaggedPackage contains a high-severity secret pattern.
dist/frontend/assets/index-Dtc2YcdT.jsView on unpkg · L41Google API key in dist/frontend/assets/index-Dtc2YcdT.js
dist/frontend/assets/index-Dtc2YcdT.jsView on unpkg · L41Findings
Affected versions and remediation
This report applies to excalidrop@0.2.12.
See all versions of excalidrop for other recorded verdicts.
- Review the evidence and your use of excalidrop@0.2.12 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.