Resource-scan receipts

bitwarden/server

Canonical URL: https://github.com/bitwarden/server · Fetched from: https://raw.githubusercontent.com/bitwarden/server/HEAD/README.md · Machine form: /v1/resource-scans/github-com-bitwarden-server-2dff89c4a3 · Markdown

Latest receipt: 3 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: 6bb0d5878a36822a5bd7051953aeceb1e22138007d49438a33ac001104573141 · 9141 bytes · scanned 2026-11-12T02:35:02.152Z · scanner resource-scan-v1 · ledger entry 36026.

The rightshold on https://github.com/bitwarden/server — scanned 2026-11-12 · 3 of 8 checks flagged · receipt rsc_5b952d096b2dbbfd616ef956, 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: bitwarden.com, contributing.bitwarden.com, docs.docker.com, func.bitwarden.com, github.com, hackerone.com, help.bitwarden.com, i.imgur.com, img.shields.io, www.docker.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: bitwarden.com; domain: contributing.bitwarden.com; domain: docs.docker.com; domain: func.bitwarden.com; domain: github.com; domain: hackerone.com; domain: help.bitwarden.com; domain: i.imgur.com; domain: img.shields.io; domain: www.docker.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: bitwarden/server; bytes scanned: 9141; fetched from: https://raw.githubusercontent.com/bitwarden/server/HEAD/README.md.

  Evidence: source host: github.com; repository: bitwarden/server; bytes scanned: 9141; fetched from: https://raw.githubusercontent.com/bitwarden/server/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 6bb0d5878a36822a… · 9141 bytes · scanner resource-scan-v1 · ledger entry 36026