Resource-scan receipts

lharries/whatsapp-mcp

Canonical URL: https://github.com/lharries/whatsapp-mcp · Fetched from: https://raw.githubusercontent.com/lharries/whatsapp-mcp/HEAD/README.md · Machine form: /v1/resource-scans/github-com-lharries-whatsapp-mcp-8e4a584f45 · Markdown

Latest receipt: 4 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: ad3e4cc17892d2ec2ad7c2ad989a174c076f8991fad305c63feb8a72b957a0cb · 9025 bytes · scanned 2026-10-27T12:21:52.295Z · scanner resource-scan-v1 · ledger entry 1563.

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: astral.sh, code.visualstudio.com, docs.google.com, github.com, modelcontextprotocol.io, simonwillison.net, www.msys2.org. 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: astral.sh; domain: code.visualstudio.com; domain: docs.google.com; domain: github.com; domain: modelcontextprotocol.io; domain: simonwillison.net; domain: www.msys2.org

• 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); download-and-execute pattern (fetched content passed to an executor in the same file). 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); download-and-execute pattern (fetched content passed to an executor in the same file)

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

  The scanned bytes match these known-bad indicators from the scanner's published pattern list: pipe-to-shell: a download piped straight into a shell interpreter; token- or credential-taking vocabulary (stealer, grabber, exfiltrate). Each match is a reproducible pattern match on the bytes named by the hash; re-running the published check on the same bytes reaches the same finding.

  Evidence: pipe-to-shell: a download piped straight into a shell interpreter; token- or credential-taking vocabulary (stealer, grabber, exfiltrate)

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

  Evidence: source host: github.com; repository: lharries/whatsapp-mcp; bytes scanned: 9025; fetched from: https://raw.githubusercontent.com/lharries/whatsapp-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 — 4 of 8 checks flagged · SHA-256 ad3e4cc17892d2ec… · 9025 bytes · scanner resource-scan-v1 · ledger entry 1563