waterloocode/laravel-validation-extend

Release historydanger

The latest release was published in April 2018, with no releases in the subsequent eight years and only five releases overall. This is strong evidence of abandonment risk for a dependency.

Project backingcaution

The repository owner is an individual user rather than an organization, and no organizational backing is shown. That leaves a thinner apparent maintenance base for an already inactive package.

Repo popularitycaution

The repository has five stars, zero forks, and zero watchers, indicating a very small user and contributor footprint. Popularity is only supporting evidence, but this provides little evidence of community resilience.

Repo toolingcaution

Composer is used for the build, but no security scanning tools are present. This is a modest transparency and maintenance gap rather than a severe risk.

Security policycaution

The repository has no security policy, leaving no documented process for receiving or disclosing vulnerabilities. This matters for a package used in application validation.