Resource-scan receipts

latest

Canonical URL: https://registry.npmjs.org/@coinbase/cdp-cli/latest · Fetched from: https://registry.npmjs.org/@coinbase/cdp-cli/latest · Machine form: /v1/resource-scans/registry-npmjs-org-coinbase-cdp-cli-latest-afb7e052bc · Markdown

Latest receipt: 3 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: b3bb3566fd8755f995f8b890ee9f4f04221c95b1500fdba70c322feb2f036a70 · 1978 bytes · scanned 2026-11-12T20:01:04.521Z · scanner resource-scan-v1 · ledger entry 38648.

The rightshold on https://registry.npmjs.org/@coinbase/cdp-cli/latest — scanned 2026-11-12 · 3 of 8 checks flagged · receipt rsc_4a6ffeff126cbdb816aeaa33, 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: docs.cdp.coinbase.com, registry.npmjs.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: docs.cdp.coinbase.com; domain: registry.npmjs.org

• Credential and environment access — pass

  No credential or environment access patterns were found in the scanned bytes.

• Install and postinstall hooks — flag

  Install-time hooks are present: package.json script "postinstall": node scripts/postinstall.mjs. A hook runs code at install time, before the resource itself is ever invoked.

  Evidence: package.json script "postinstall": node scripts/postinstall.mjs

• Obfuscation and encoded payloads — pass

  No obfuscation or encoded-payload signs were found in the scanned bytes.

• 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 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: registry.npmjs.org; gist artifact; bytes scanned: 1978.

  Evidence: source host: registry.npmjs.org; gist artifact; bytes scanned: 1978

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 b3bb3566fd8755f9… · 1978 bytes · scanner resource-scan-v1 · ledger entry 38648