Resource-scan receipts

executeautomation/mcp-playwright

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

Latest receipt: 3 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: 2ba1c85ad3facbe144b8b94d6d3256c45c3e43a0073a683073ff03d55aa9a8c3 · 11231 bytes · scanned 2026-10-27T12:21:10.602Z · scanner resource-scan-v1 · ledger entry 1541.

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, archestra.ai, executeautomation.github.io, glama.ai, img.shields.io, insiders.vscode.dev, mseep.ai, mseep.net, smithery.ai, star-history.com, www.mcpevals.io. 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: archestra.ai; domain: executeautomation.github.io; domain: glama.ai; domain: img.shields.io; domain: insiders.vscode.dev; domain: mseep.ai; domain: mseep.net; domain: smithery.ai; domain: star-history.com; domain: www.mcpevals.io

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

  Evidence: source host: github.com; repository: executeautomation/mcp-playwright; bytes scanned: 11231; fetched from: https://raw.githubusercontent.com/executeautomation/mcp-playwright/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 2ba1c85ad3facbe1… · 11231 bytes · scanner resource-scan-v1 · ledger entry 1541