codelytv/criteria-from-laravel-request-to-eloquent

Release historydanger

The package has had no release in over two years: four releases were published within roughly one day in August 2024, followed by zero releases in the last 12 months. This strongly suggests abandonment risk.

Repo commit activitydanger

The repository has recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and limited evidence of ongoing maintenance.

Licensecaution

No license is declared, and neither the package nor the linked repository contains a recognized license file. This creates a material legal and transparency gap for adoption.

Package file treecaution

The release contains only README.md, composer.json, and one source file, with no additional project structure. That can be valid for a small adapter, but it leaves little evidence of testing or maintenance depth.

Repo toolingcaution

Composer is used as the build tool, which fits the package ecosystem, but no security scanning tools are present. The missing scanning is a modest hygiene concern rather than a standalone adoption blocker.