Show HN: I built a health score for 1,800 Laravel packages (opens in new tab)

Hi HN,

I'm Daniel, a solo dev from Italy. I built LaraPlugins.io to solve a specific pain point I kept hitting: finding a Laravel package, installing it, and only realizing weeks later that it was abandoned or incompatible with the latest PHP version.

It’s a directory that assigns an automated "Health Score" to packages based on maintenance, testing, and community signals (not just popularity).

The Stack:

    Backend: Laravel running on Octane (FrankenPhp) for high performance.

    Admin: Filament PHP (which has been a joy to work with).

    Queues: Heavy use of Redis queues to ingest stats from Packagist/GitHub in the background and also for the heavy cache usage i applied. 

    Cloudflare: Everything is cached in cloudflare after the first load so even big traffic should not impact the server machine directly. 

    Workers: Managed via Laravel Horizon running in a single Docker container.

    Frontend: Blade templates + Tailwind CSS.

The hardest part was tuning the scoring algorithm to not penalize "finished" stable packages while correctly flagging abandoned ones. I'm still tweaking the weights, so I'd love to hear if the score for your favorite package feels accurate or off.