Resource-scan receipts

openreplay/openreplay

Canonical URL: https://github.com/openreplay/openreplay · Fetched from: https://raw.githubusercontent.com/openreplay/openreplay/HEAD/README.md · Machine form: /v1/resource-scans/github-com-openreplay-openreplay-42ed694a35 · Markdown

Latest receipt: 2 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: 077bd325ea7bca9dc2efac15315b7c198b9f03afa5b88d1bf76d90d536644a14 · 13481 bytes · scanned 2026-11-12T02:49:13.834Z · scanner resource-scan-v1 · ledger entry 36077.

The rightshold on https://github.com/openreplay/openreplay — scanned 2026-11-12 · 2 of 8 checks flagged · receipt rsc_a2b9cdd43713aa452d15bd19, 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: blog.openreplay.com, docs.openreplay.com, forum.openreplay.com, github.com, img.shields.io, openreplay.com, slack.openreplay.com, www.youtube.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: blog.openreplay.com; domain: docs.openreplay.com; domain: forum.openreplay.com; domain: github.com; domain: img.shields.io; domain: openreplay.com; domain: slack.openreplay.com; domain: www.youtube.com; HTTP client library references

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

  Evidence: source host: github.com; repository: openreplay/openreplay; bytes scanned: 13481; fetched from: https://raw.githubusercontent.com/openreplay/openreplay/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 077bd325ea7bca9d… · 13481 bytes · scanner resource-scan-v1 · ledger entry 36077