Resource-scan receipts

foundry-rs/foundry

Canonical URL: https://raw.githubusercontent.com/foundry-rs/foundry/refs/heads/master/foundryup/install · Fetched from: https://raw.githubusercontent.com/foundry-rs/foundry/refs/heads/master/foundryup/install · Machine form: /v1/resource-scans/raw-githubusercontent-com-foundry-rs-foundry-refs-heads-525f8a93b1 · Markdown

Latest receipt: 3 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: 79f6daf710d01bdd3a17540f3049eed3dd1fd52cc3ec42c939a38eee4a55acfd · 1038 bytes · scanned 2026-10-27T23:33:59.362Z · scanner resource-scan-v1 · ledger entry 1988.

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: raw.githubusercontent.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: raw.githubusercontent.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). 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: raw.githubusercontent.com; repository: foundry-rs/foundry; bytes scanned: 1038.

  Evidence: source host: raw.githubusercontent.com; repository: foundry-rs/foundry; bytes scanned: 1038

History

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

• 2026-10-27 — 3 of 8 checks flagged · SHA-256 79f6daf710d01bdd… · 1038 bytes · scanner resource-scan-v1 · ledger entry 1988