Resource-scan receipts

zubair-trabzada/geo-seo-claude

Canonical URL: https://github.com/zubair-trabzada/geo-seo-claude · Fetched from: https://raw.githubusercontent.com/zubair-trabzada/geo-seo-claude/HEAD/README.md · Machine form: /v1/resource-scans/github-com-zubair-trabzada-geo-seo-claude-a3b183624a · Markdown

Latest receipt: 4 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: 6ee85c5466a3c4d5b5573f5055de275e5a0a5ca6298332b393942cd60930f687 · 10794 bytes · scanned 2026-10-27T12:26:50.826Z · scanner resource-scan-v1 · ledger entry 1683.

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, docs.astral.sh, example.com, git-scm.com, github.com, raw.githubusercontent.com, skool.com, www.star-history.com. 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: docs.astral.sh; domain: example.com; domain: git-scm.com; domain: github.com; domain: raw.githubusercontent.com; domain: skool.com; domain: www.star-history.com

• 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. 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

• 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: zubair-trabzada/geo-seo-claude; bytes scanned: 10794; fetched from: https://raw.githubusercontent.com/zubair-trabzada/geo-seo-claude/HEAD/README.md.

  Evidence: source host: github.com; repository: zubair-trabzada/geo-seo-claude; bytes scanned: 10794; fetched from: https://raw.githubusercontent.com/zubair-trabzada/geo-seo-claude/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 6ee85c5466a3c4d5… · 10794 bytes · scanner resource-scan-v1 · ledger entry 1683