Resource-scan receipts

WireGuard/wireguard-go

Canonical URL: https://github.com/WireGuard/wireguard-go · Fetched from: https://raw.githubusercontent.com/WireGuard/wireguard-go/HEAD/README.md · Machine form: /v1/resource-scans/github-com-wireguard-wireguard-go-9900f69d37 · Markdown

Latest receipt: 2 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: b71a3690a654a4ef4571564c2d740f3074e9e1730f8837499058c51960c3bd43 · 3913 bytes · scanned 2026-11-12T02:36:18.168Z · scanner resource-scan-v1 · ledger entry 36041.

The rightshold on https://github.com/WireGuard/wireguard-go — scanned 2026-11-12 · 2 of 8 checks flagged · receipt rsc_1d4ebf949112f55452981c70, 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: git.zx2c4.com, go.dev, www.wireguard.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: git.zx2c4.com; domain: go.dev; domain: www.wireguard.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 — 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: WireGuard/wireguard-go; bytes scanned: 3913; fetched from: https://raw.githubusercontent.com/WireGuard/wireguard-go/HEAD/README.md.

  Evidence: source host: github.com; repository: WireGuard/wireguard-go; bytes scanned: 3913; fetched from: https://raw.githubusercontent.com/WireGuard/wireguard-go/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-12 — 2 of 8 checks flagged · SHA-256 b71a3690a654a4ef… · 3913 bytes · scanner resource-scan-v1 · ledger entry 36041