Resource-scan receipts

upstash/context7

Canonical URL: https://github.com/upstash/context7 · Fetched from: https://raw.githubusercontent.com/upstash/context7/HEAD/README.md · Machine form: /v1/resource-scans/github-com-upstash-context7-16a7277d62 · Markdown

Latest receipt: 4 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: 387e015c40c4541d966e754525e626cfbbb0482f66c9a00246d956c943886548 · 13026 bytes · scanned 2026-10-27T12:18:59.918Z · scanner resource-scan-v1 · ledger entry 1510.

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: chatgpt.com, claude.ai, context7.com, cursor.com, github.com, img.shields.io, marketplace.visualstudio.com, mcp.context7.com, upstash.com, www.npmjs.com, www.youtube.com, x.com, youtu.be. 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: chatgpt.com; domain: claude.ai; domain: context7.com; domain: cursor.com; domain: github.com; domain: img.shields.io; domain: marketplace.visualstudio.com; domain: mcp.context7.com; domain: upstash.com; domain: www.npmjs.com; domain: www.youtube.com; domain: x.com; domain: youtu.be

• Credential and environment access — flag

  The scanned bytes contain credential or environment access patterns: secret-named variables (API_KEY, SECRET, TOKEN, PASSWORD and similar names); authorization headers and bearer values. The receipt names the pattern kinds only; no credential value is reproduced here.

  Evidence: secret-named variables (API_KEY, SECRET, TOKEN, PASSWORD and similar names); authorization headers and bearer values

• Install and postinstall hooks — pass

  No install or postinstall hooks were found in the scanned bytes.

• Obfuscation and encoded payloads — flag

  The scanned bytes carry obfuscation or encoding signs: 2 long base64-shaped runs (120+ characters). Encoded content cannot be read from the bytes alone, so what it does cannot be checked from the bytes alone either.

  Evidence: 2 long base64-shaped runs (120+ characters)

• 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, credentials behavior, and no permissions declaration was found in the scanned bytes to compare it against.

  Evidence: behavior: network; behavior: credentials

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

  Evidence: source host: github.com; repository: upstash/context7; bytes scanned: 13026; fetched from: https://raw.githubusercontent.com/upstash/context7/HEAD/README.md

History

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

• 2026-10-27 — 4 of 8 checks flagged · SHA-256 387e015c40c4541d… · 13026 bytes · scanner resource-scan-v1 · ledger entry 1510