# Resource-scan receipt: install

A resource-scan receipt is the record of one static check run over one public AI resource — a repository, a gist, a skill file, a script, an MCP server package or a config — at the public URL named on the receipt. The receipt binds to the exact bytes scanned, named by their SHA-256 hash, and is sealed into the public ledger like every other record here. Each receipt carries the published check list with the outcome of every check and the findings in plain language. The analysis is static only: the bytes are read as text and are never executed, installed or run, and nothing is fetched from behind a login. A receipt publishes evidence, never a judgment: the summary line counts how many of the checks flagged, and the reader draws their own conclusion from the findings. Re-scanning the same URL creates a new receipt; the artifact page shows the latest receipt and the history, and when the bytes at a URL change the new receipt is a new version — no receipt is ever edited or overwritten.

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.

Artifact: install
Canonical URL: https://cli.sentry.dev/install
Fetched from: https://cli.sentry.dev/install
SHA-256 of the exact bytes scanned: 730cc74c43be08c6a1c2595c6d0a694ce3a8b7072d0588738937152d7d2078e6
Bytes scanned: 18578 · Scanned: 2026-11-06T03:16:59.907Z · Scanner: resource-scan-v1
Summary: 6 of 8 checks flagged (evidence only — the findings below are the record)
Analysis: static only — the bytes were read as text and were never executed, installed or run.
Ledger entry: 15020

## 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 (1 receipt, 1 version)

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

Machine form: https://www.rightshold.com/v1/resource-scans/cli-sentry-dev-install-4128f87a64