Resource-scan receipts

Ryze-AI-Adgent/open-seo-mcp-skills

Canonical URL: https://github.com/Ryze-AI-Adgent/open-seo-mcp-skills · Fetched from: https://raw.githubusercontent.com/Ryze-AI-Adgent/open-seo-mcp-skills/HEAD/README.md · Machine form: /v1/resource-scans/github-com-ryze-ai-adgent-open-seo-mcp-skills-f9a663354c · Markdown

Latest receipt: 2 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: e064de2b643cd9f78e444404db662557c684d7060b7fbfad8d58e2a5facd9ceb · 6663 bytes · scanned 2026-10-27T12:27:27.086Z · scanner resource-scan-v1 · ledger entry 1703.

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: connector.get-ryze.ai, github.com, raw.githubusercontent.com, www.get-ryze.ai. 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: connector.get-ryze.ai; domain: github.com; domain: raw.githubusercontent.com; domain: www.get-ryze.ai

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

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

• 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 — 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: Ryze-AI-Adgent/open-seo-mcp-skills; bytes scanned: 6663; fetched from: https://raw.githubusercontent.com/Ryze-AI-Adgent/open-seo-mcp-skills/HEAD/README.md.

  Evidence: source host: github.com; repository: Ryze-AI-Adgent/open-seo-mcp-skills; bytes scanned: 6663; fetched from: https://raw.githubusercontent.com/Ryze-AI-Adgent/open-seo-mcp-skills/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 — 2 of 8 checks flagged · SHA-256 e064de2b643cd9f7… · 6663 bytes · scanner resource-scan-v1 · ledger entry 1703