Resource-scan receipts

yctimlin/mcp_excalidraw

Canonical URL: https://github.com/yctimlin/mcp_excalidraw · Fetched from: https://raw.githubusercontent.com/yctimlin/mcp_excalidraw/HEAD/README.md · Machine form: /v1/resource-scans/github-com-yctimlin-mcp-excalidraw-9cbd5e2875 · Markdown

Latest receipt: 3 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: f17f96ff2cb2915fad43074418477716d9c0186ba8b3ebaa34c99b250478c774 · 39723 bytes · scanned 2026-10-27T12:23:31.804Z · scanner resource-scan-v1 · ledger entry 1609.

Analysis is static only: the bytes were read as text and were never executed, installed or run. Nothing was fetched from behind a login.

Checks (latest receipt)

• Outbound network references — flag

  The scanned bytes reference outbound network activity to these domains: draw.example.com, excalidraw.com, github.com, host.docker.internal, img.shields.io, json.excalidraw.com, opencode.ai, www.npmjs.com, x.com, youtu.be. Any resource that reaches the network can send data out as well as bring data in; the findings name what the bytes reference, and the reader decides whether that fits the resource's stated purpose.

  Evidence: domain: draw.example.com; domain: excalidraw.com; domain: github.com; domain: host.docker.internal; domain: img.shields.io; domain: json.excalidraw.com; domain: opencode.ai; domain: www.npmjs.com; domain: x.com; domain: youtu.be; HTTP client library references

• Credential and environment access — pass

  No credential or environment access patterns were found in the scanned bytes.

• Install and postinstall hooks — pass

  No install or postinstall hooks were found in the scanned bytes.

• Obfuscation and encoded payloads — pass

  No obfuscation or encoded-payload signs were found in the scanned bytes.

• Shell-outs and download-and-execute — flag

  The scanned bytes contain shell-out or download patterns: shell command tools named in the bytes (curl, wget, powershell). Code that runs shell commands acts with the full permissions of whoever runs it.

  Evidence: shell command tools named in the bytes (curl, wget, powershell)

• Permission declarations vs behavior — flag

  The bytes show network behavior, and no permissions declaration was found in the scanned bytes to compare it against.

  Evidence: behavior: network

• Known-bad indicators — pass

  None of the scanner's published known-bad indicator patterns matched the scanned bytes.

• Provenance facts (weak signals) — pass

  Provenance facts, labeled weak signals — they say where the bytes sit, not what the bytes do: source host: github.com; repository: yctimlin/mcp_excalidraw; bytes scanned: 39723; fetched from: https://raw.githubusercontent.com/yctimlin/mcp_excalidraw/HEAD/README.md.

  Evidence: source host: github.com; repository: yctimlin/mcp_excalidraw; bytes scanned: 39723; fetched from: https://raw.githubusercontent.com/yctimlin/mcp_excalidraw/HEAD/README.md

History

Every receipt for this artifact so far names the same SHA-256: the bytes have not changed between scans.

• 2026-10-27 — 3 of 8 checks flagged · SHA-256 f17f96ff2cb2915f… · 39723 bytes · scanner resource-scan-v1 · ledger entry 1609