rasulian/laravel-user-verification

Release historydanger

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

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's long release gap and indicating no current maintenance capacity.

Maintainerscaution

Only one account has registry publishing access. That is not inherently unhealthy for a small package, but it leaves limited visible publishing redundancy alongside the lack of recent project activity.

Repo issue activitycaution

There has been no issue or pull-request activity in the last month, and one issue remains open. This adds a smaller maintenance concern but is less decisive than the absent release and commit activity.

Repo toolingcaution

The repository uses Composer but reports no security scanning tools. This is a modest transparency and maintenance gap, not a severe risk by itself.