Resource-scan receipts

microsoft/playwright-mcp

Canonical URL: https://github.com/microsoft/playwright-mcp · Fetched from: https://raw.githubusercontent.com/microsoft/playwright-mcp/HEAD/README.md · Machine form: /v1/resource-scans/github-com-microsoft-playwright-mcp-ba31bde2df · Markdown

Latest receipt: 3 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: b33aa71a13d655e96e6b736d0c9de1e5ddea52f205916ca20b876387ff830e87 · 66837 bytes · scanned 2026-10-27T12:21:08.250Z · scanner resource-scan-v1 · ledger entry 1540.

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: block.github.io, code.visualstudio.com, cursor.com, docs.cline.bot, docs.factory.ai, docs.github.com, docs.qodo.ai, docs.warp.dev, docs.windsurf.com, docs.x.ai, example.com, files.lmstudio.ai, github.com, img.shields.io, insiders.vscode.dev, junie.jetbrains.com, kiro.dev, lmstudio.ai, modelcontextprotocol.io, opencode.ai, playwright.dev. 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: block.github.io; domain: code.visualstudio.com; domain: cursor.com; domain: docs.cline.bot; domain: docs.factory.ai; domain: docs.github.com; domain: docs.qodo.ai; domain: docs.warp.dev; domain: docs.windsurf.com; domain: docs.x.ai; domain: example.com; domain: files.lmstudio.ai; domain: github.com; domain: img.shields.io; domain: insiders.vscode.dev; domain: junie.jetbrains.com; domain: kiro.dev; domain: lmstudio.ai; domain: modelcontextprotocol.io; domain: opencode.ai; domain: playwright.dev

• 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: microsoft/playwright-mcp; bytes scanned: 66837; fetched from: https://raw.githubusercontent.com/microsoft/playwright-mcp/HEAD/README.md.

  Evidence: source host: github.com; repository: microsoft/playwright-mcp; bytes scanned: 66837; fetched from: https://raw.githubusercontent.com/microsoft/playwright-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 b33aa71a13d655e9… · 66837 bytes · scanner resource-scan-v1 · ledger entry 1540