alexandrebulete/laravel-benchmark

Maintainerscaution

The registry has one publishing maintainer. That is a narrow publishing base for a user-owned project and increases continuity risk when the repository also shows no recent activity.

Project backingcaution

The package is backed by a personal repository rather than an organization, so the single-maintainer signal is not compensated by visible organizational backing.

Release historycaution

The package has four releases, all concentrated within about 12 hours, followed by roughly nine months without a new release. That short history and long pause reduce confidence in ongoing maintenance.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months, consistent with a project that has been inactive for about nine months.

Repo popularitycaution

Two stars and one fork show limited external adoption. Popularity is only supporting evidence, but this provides little community signal to offset the maintenance pause.