Resource-scan receipts

docusealco/docuseal

Canonical URL: https://github.com/docusealco/docuseal · Fetched from: https://raw.githubusercontent.com/docusealco/docuseal/HEAD/README.md · Machine form: /v1/resource-scans/github-com-docusealco-docuseal-e97eb46dbf · Markdown

Latest receipt: 3 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: 04ded3c4291b9052cf5b6f4ff5cfa34fc5fd13950b5bfb3ce921a3a9a292d11f · 5795 bytes · scanned 2026-11-12T02:42:40.839Z · scanner resource-scan-v1 · ledger entry 36058.

The rightshold on https://github.com/docusealco/docuseal — scanned 2026-11-12 · 3 of 8 checks flagged · receipt rsc_bc68ece6ea87e92d21b14065, 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: apps.apple.com, cloud.digitalocean.com, demo.docuseal.tech, discord.gg, docuseal.com, github.com, heroku.com, hub.docker.com, img.shields.io, play.google.com, railway.app, railway.com, raw.githubusercontent.com, render.com, twitter.com, www.deploytodo.com, www.docuseal.com, www.herokucdn.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: apps.apple.com; domain: cloud.digitalocean.com; domain: demo.docuseal.tech; domain: discord.gg; domain: docuseal.com; domain: github.com; domain: heroku.com; domain: hub.docker.com; domain: img.shields.io; domain: play.google.com; domain: railway.app; domain: railway.com; domain: raw.githubusercontent.com; domain: render.com; domain: twitter.com; domain: www.deploytodo.com; domain: www.docuseal.com; domain: www.herokucdn.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: github.com; repository: docusealco/docuseal; bytes scanned: 5795; fetched from: https://raw.githubusercontent.com/docusealco/docuseal/HEAD/README.md.

  Evidence: source host: github.com; repository: docusealco/docuseal; bytes scanned: 5795; fetched from: https://raw.githubusercontent.com/docusealco/docuseal/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 — 3 of 8 checks flagged · SHA-256 04ded3c4291b9052… · 5795 bytes · scanner resource-scan-v1 · ledger entry 36058