gmsth/laravel-oop-validation

Release historydanger

The package has had only one release, published in December 2019, with no releases in the last 12 months. This is strong evidence of abandonment risk for a package intended as a Laravel dependency.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no activity since 2019.

Licensecaution

No license is declared, and neither the package artifact nor the linked repository contains a recognized license file. This creates a real adoption and transparency concern.

Package file treecaution

The artifact contains only four files and the repository only six, indicating a very small project with little supporting documentation or infrastructure. The small footprint is not inherently unsafe, but it limits evidence of maturity.

Repo toolingcaution

Composer is used for the build, which is appropriate, but no security scanning tools are present. For a small inactive package, this leaves little evidence of ongoing supply-chain hygiene.