Resource-scan receipts

thedotmack/claude-mem

Canonical URL: https://github.com/thedotmack/claude-mem · Fetched from: https://raw.githubusercontent.com/thedotmack/claude-mem/HEAD/README.md · Machine form: /v1/resource-scans/github-com-thedotmack-claude-mem-853c63f738 · Markdown

Latest receipt: 4 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: 48a9ed930aadd77cbfe3027180a271084307816a9583f213c4f600e97f706f43 · 20457 bytes · scanned 2026-10-27T12:27:14.565Z · scanner resource-scan-v1 · ledger entry 1696.

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: api.star-history.com, awesome.re, claude.com, cmem.ai, discord.com, docs.claude-mem.ai, github.com, img.shields.io, install.cmem.ai, nodejs.org, openclaw.ai, raw.githubusercontent.com, trendshift.io, vercel.com, www.star-history.com, x.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: api.star-history.com; domain: awesome.re; domain: claude.com; domain: cmem.ai; domain: discord.com; domain: docs.claude-mem.ai; domain: github.com; domain: img.shields.io; domain: install.cmem.ai; domain: nodejs.org; domain: openclaw.ai; domain: raw.githubusercontent.com; domain: trendshift.io; domain: vercel.com; domain: www.star-history.com; domain: x.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); download-and-execute pattern (fetched content passed to an executor in the same file). 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); download-and-execute pattern (fetched content passed to an executor in the same file)

• 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 — flag

  The scanned bytes match these known-bad indicators from the scanner's published pattern list: pipe-to-shell: a download piped straight into a shell interpreter. Each match is a reproducible pattern match on the bytes named by the hash; re-running the published check on the same bytes reaches the same finding.

  Evidence: pipe-to-shell: a download piped straight into a shell interpreter

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

  Evidence: source host: github.com; repository: thedotmack/claude-mem; bytes scanned: 20457; fetched from: https://raw.githubusercontent.com/thedotmack/claude-mem/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 48a9ed930aadd77c… · 20457 bytes · scanner resource-scan-v1 · ledger entry 1696