Resource-scan receipts

install

Canonical URL: https://cli.sentry.dev/install · Fetched from: https://cli.sentry.dev/install · Machine form: /v1/resource-scans/cli-sentry-dev-install-4128f87a64 · Markdown

Latest receipt: 6 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: 730cc74c43be08c6a1c2595c6d0a694ce3a8b7072d0588738937152d7d2078e6 · 18578 bytes · scanned 2026-11-06T03:16:59.907Z · scanner resource-scan-v1 · ledger entry 15020.

The rightshold on https://cli.sentry.dev/install — scanned 2026-11-06 · 6 of 8 checks flagged · receipt rsc_882686507734b0ea4b290a29, 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: api.github.com, cli.sentry.dev, ghcr.io, github.com, o1.ingest.us.sentry.io, release-registry.services.sentry.io. 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.github.com; domain: cli.sentry.dev; domain: ghcr.io; domain: github.com; domain: o1.ingest.us.sentry.io; domain: release-registry.services.sentry.io

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

  Evidence: behavior: network; behavior: credentials

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

  Only partial provenance facts could be read from the URL — a weak signal, recorded as such: source host: cli.sentry.dev; bytes scanned: 18578.

  Evidence: source host: cli.sentry.dev; bytes scanned: 18578

History

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

• 2026-11-06 — 6 of 8 checks flagged · SHA-256 730cc74c43be08c6… · 18578 bytes · scanner resource-scan-v1 · ledger entry 15020