Resource-scan receipts

imessage-agents

Canonical URL: https://flow.engineer/imessage-agents · Fetched from: https://flow.engineer/imessage-agents · Machine form: /v1/resource-scans/flow-engineer-imessage-agents-753e7fc6e4 · Markdown

Latest receipt: 5 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: 870f349a96e2eaf3fed296fb51977f71b6176cc7f5ec0fda232e2a740c7b08a4 · 233252 bytes · scanned 2026-10-28T04:03:14.761Z · scanner resource-scan-v1 · ledger entry 2098.

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.flow.engineer, calendar.app.google, flow.engineer, fonts.googleapis.com, fonts.gstatic.com, github.com, schema.org, www.npmjs.com, www.w3.org. 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.flow.engineer; domain: calendar.app.google; domain: flow.engineer; domain: fonts.googleapis.com; domain: fonts.gstatic.com; domain: github.com; domain: schema.org; domain: www.npmjs.com; domain: www.w3.org

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

  Only partial provenance facts could be read from the URL — a weak signal, recorded as such: source host: flow.engineer; bytes scanned: 233252.

  Evidence: source host: flow.engineer; bytes scanned: 233252

History

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

• 2026-10-28 — 5 of 8 checks flagged · SHA-256 870f349a96e2eaf3… · 233252 bytes · scanner resource-scan-v1 · ledger entry 2098