Resource-scan receipts

signal-forge-ai/x402-agent-tools

Canonical URL: https://github.com/signal-forge-ai/x402-agent-tools · Fetched from: https://raw.githubusercontent.com/signal-forge-ai/x402-agent-tools/HEAD/README.md · Machine form: /v1/resource-scans/github-com-signal-forge-ai-x402-agent-tools-764eccdcd6 · Markdown

Latest receipt: 3 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: 07d970cdc136a4fa54a565c220de05bf2dfb759209a71c07f6c8d8bebd72fc9b · 4464 bytes · scanned 2026-11-03T07:31:58.423Z · scanner resource-scan-v1 · ledger entry 6422.

The rightshold on https://github.com/signal-forge-ai/x402-agent-tools — scanned 2026-11-03 · 3 of 8 checks flagged · receipt rsc_54270bfdbf99e11446ca762b, verify at rightshold.com/verify.

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: example.com, x402-agent-tools.x402agenttools.workers.dev, x402.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: example.com; domain: x402-agent-tools.x402agenttools.workers.dev; domain: x402.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). 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)

• 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: signal-forge-ai/x402-agent-tools; bytes scanned: 4464; fetched from: https://raw.githubusercontent.com/signal-forge-ai/x402-agent-tools/HEAD/README.md.

  Evidence: source host: github.com; repository: signal-forge-ai/x402-agent-tools; bytes scanned: 4464; fetched from: https://raw.githubusercontent.com/signal-forge-ai/x402-agent-tools/HEAD/README.md

History

Every receipt for this artifact so far names the same SHA-256: the bytes have not changed between scans.

• 2026-11-03 — 3 of 8 checks flagged · SHA-256 07d970cdc136a4fa… · 4464 bytes · scanner resource-scan-v1 · ledger entry 6422