In fact, so much so, That I picked up an appropriately named domain, created an identical (search) page. Created a CPAN mirror ( soon to be official ). All that's left (and this is pretty important) is the search implementation.
Time is running short. The 25th is drawing near. Anyone willing to help; suggest how I might best (re)create the search implementation. As I understand it, it's not open(source), or available. :-(

I'd like to implement search.cpan.org

Thank you very very much!

All that's left (and this is pretty important) is the search implementation.

Forget the search engine. Since meta is the hub just cheat and use their API!

github.com/metacpan/metacpan-api/blob/master/docs/API-docs.md

Thanks for the reply (and link) !

I've examined Gabor Szabo' SCO
source:
MetaCPAN-SCO
his article:
Building an open source clone of search.cpan.org using the MetaCPAN API
which looks promising. But seems to require running a service on it's own port. Which I'd like to avoid. While I guess I could (re)process metacpans data. That seems grossly inefficient, and slow. especially given I'm already running a mirror. Seems it'd be a whole lot smarter to simply pull the data from my own copy and process that. Maybe populating a DB with it, and pulling it from there. This lead me to:
App::CPAN::Search
and
Package::Locator
but they're more Package centric, rather than: module | dist | author , as search, and metacpan do
like:
CPAN::SQLite
but I don't think it'll scale well. But there's also:
CPAN::Search::Lite
which seems a bit closer, and might scale better, as well.

Anyway, that's as far as I've managed so far. But was hoping to I might find a quick "drop in" replacement I might implement.

Thanks again!

¡λɐp ʇɑəɹ⅁ ɐ əʌɐɥ puɐ ʻꜱdləɥ ꜱᴉɥʇ ədoH