Resource-scan receipts

GLips/Figma-Context-MCP

Canonical URL: https://github.com/GLips/Figma-Context-MCP · Fetched from: https://raw.githubusercontent.com/GLips/Figma-Context-MCP/HEAD/README.md · Machine form: /v1/resource-scans/github-com-glips-figma-context-mcp-6a29cb753b · Markdown

Latest receipt: 3 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: 2475bde5427179d421a83ff4f45451b8c5095206fa595e6ce3f7abb7fb867c51 · 4186 bytes · scanned 2026-10-27T12:21:41.525Z · scanner resource-scan-v1 · ledger entry 1557.

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: api.star-history.com, cursor.sh, framelink.ai, github.com, help.figma.com, img.shields.io, img.youtube.com, modelcontextprotocol.io, npmcharts.com, star-history.com, twitter.com, www.figma.com, www.framelink.ai, 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: api.star-history.com; domain: cursor.sh; domain: framelink.ai; domain: github.com; domain: help.figma.com; domain: img.shields.io; domain: img.youtube.com; domain: modelcontextprotocol.io; domain: npmcharts.com; domain: star-history.com; domain: twitter.com; domain: www.figma.com; domain: www.framelink.ai; domain: youtu.be

• Credential and environment access — flag

  The scanned bytes contain credential or environment access patterns: secret-named variables (API_KEY, SECRET, TOKEN, PASSWORD and similar names). The receipt names the pattern kinds only; no credential value is reproduced here.

  Evidence: secret-named variables (API_KEY, SECRET, TOKEN, PASSWORD and similar names)

• 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 — pass

  No shell-out or download-and-execute patterns were found in the scanned bytes.

• Permission declarations vs behavior — flag

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

  Evidence: behavior: network; behavior: credentials

• 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: GLips/Figma-Context-MCP; bytes scanned: 4186; fetched from: https://raw.githubusercontent.com/GLips/Figma-Context-MCP/HEAD/README.md.

  Evidence: source host: github.com; repository: GLips/Figma-Context-MCP; bytes scanned: 4186; fetched from: https://raw.githubusercontent.com/GLips/Figma-Context-MCP/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 2475bde5427179d4… · 4186 bytes · scanner resource-scan-v1 · ledger entry 1557