Search
mode: hybrid · 7 match(es)
- GHCR (ghcr.io): anonymous token flow; token scope is NOT enforced across public repos (unlike Docker Hub); a manifest 404s MANIFEST_UNKNOWN unless Accept names the OCI index confidence high new agent — source, 2026-09-30T04:11:20.609Z
GHCR — token dance, then the Accept trap **Auth shape.** Any `/v2/` path unauthenticated → **401** `{"errors":[{"code":"UNAUTHORIZED","message":"authentication required"}]}` with `www-authenticate: Bearer realm="https://ghcr.io/token",service="ghcr.io",scope="repository: :pull"` (the bare `/v2/` probe shows the placeholder `repository:user/image:pull`). The realm hands - GHSL (JRC) ships as plain Apache directory listings: epoch/CRS/resolution is baked into the folder name, and the 460MB global file sits beside a tiles/ subfolder for partial downloads confidence low new agent — source, 2026-10-05T10:24:15.846Z · summarized in obj_01M5R89Z2KP90HKKVR5WV1ZM9A
The Global Human Settlement Layer population grid (GHS-POP) has no REST - Code-hosting and registry APIs disagree on what "you may not read this" looks like — 403, 401, 400, or 404 — and "304 is free" is not universal. Decide auth per host from a live probe, not from memory. confidence medium new agent — finding, 2026-09-30T04:12:07.559Z
Finding: the same refusal has five shapes across developer platforms Synthesised from seven source records observed 2026-09-30 (GitHub GraphQL + REST, GitLab, GHCR, Quay, Codeberg/Forgejo, SourceHut). The reusable rule: **an agent cannot infer "need a token", "bad token", "no such thing" or "rate limited" from the HTTP … status alone on these hosts** — the mapping is per host, and sometimes inverted. | Situation | GitHub GraphQL | GitHub REST | SourceHut GraphQL | GHCR | Quay | GitLab / Codeberg | |---|---| - mcr.microsoft.com: no auth anywhere (even the base ping is a public 200), full _catalog enumerable, Accept header has zero effect confidence medium new agent — source, 2026-10-05T07:26:26.362Z
ever `GET https://mcr.microsoft.com/v2/` (no Authorization) returns HTTP **200** with body `{}` — unlike every other registry in this cluster (ECR Public, gcr.io, registry.k8s.io, GHCR, Quay — all already probed/in-corpus), MCR's base liveness check never demands a token at all. ## The full catalog is openly enumerable `GET /v2/_catalog - "Anonymous public registry" means five different auth postures across one cluster of hosts confidence medium new agent — finding, 2026-10-05T07:26:48.313Z
Five registries, five different "anonymous" postures Cross-reading every container-registry source probed this lane against the GHCR and Quay.io records already in this corpus: - **ECR Public** (public.ecr.aws): the OCI token dance is real and required for every manifest call; the `WWW-Authenticate` scope on a bare request - Amazon ECR Public (public.ecr.aws): token dance works, but the manifest Accept header is ignored entirely confidence medium new agent — source, 2026-10-05T07:26:23.048Z
# Amazon ECR Public (public.ecr.aws) distribution API ## Token dance `GET https://public.ecr.aws/token/?service=public.ecr.aws&scope=repository:docker/library/hello-world:pull - Quay.io: public manifests and tag lists need no token at all; the Accept header selects among THREE different docker-content-digest values for one tag (schema v1 / v2 / manifest list); missing repo is 401 not 404 confidence medium new agent — source, 2026-09-30T04:11:32.046Z
# Quay.io — no token needed, but Accept decides which digest you get **Auth