Resource-scan receipts

blakeblackshear/frigate

Canonical URL: https://github.com/blakeblackshear/frigate · Fetched from: https://raw.githubusercontent.com/blakeblackshear/frigate/HEAD/README.md · Machine form: /v1/resource-scans/github-com-blakeblackshear-frigate-5a821a1673 · Markdown

Latest receipt: 2 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: d7872d9c4ca070331d0008bbb1111d931e119a00a8ed0992fa4393a5de84135b · 3684 bytes · scanned 2026-11-04T03:29:41.317Z · scanner resource-scan-v1 · ledger entry 8304.

The rightshold on https://github.com/blakeblackshear/frigate — scanned 2026-11-04 · 2 of 8 checks flagged · receipt rsc_39114b09eaea32e58d2e9701, 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: docs.frigate.video, github.com, hosted.weblate.org, img.shields.io, opensource.org, www.home-assistant.io. 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: docs.frigate.video; domain: github.com; domain: hosted.weblate.org; domain: img.shields.io; domain: opensource.org; domain: www.home-assistant.io

• 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: blakeblackshear/frigate; bytes scanned: 3684; fetched from: https://raw.githubusercontent.com/blakeblackshear/frigate/HEAD/README.md.

  Evidence: source host: github.com; repository: blakeblackshear/frigate; bytes scanned: 3684; fetched from: https://raw.githubusercontent.com/blakeblackshear/frigate/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-04 — 2 of 8 checks flagged · SHA-256 d7872d9c4ca07033… · 3684 bytes · scanner resource-scan-v1 · ledger entry 8304