kakajan/laravel-jalali

Release historydanger

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

Repo commit activitydanger

There were no commits and no active maintainers in the last 3 months, while the repository's last push was in October 2017. This confirms the release-history concern and materially raises abandonment risk.

Maintainerscaution

One registry account has publish access. This is a thin publishing base, though the linked repository is owned by the same individual, so it does not independently establish abandonment.

Project backingcaution

The registry namespace and repository owner are the same individual account, and no organization backing is shown. This is consistent ownership but leaves a narrow maintainer base.

Repo issue activitycaution

There are no open issues or pull requests and no recent activity. The empty queue is neutral, but it also provides no evidence of ongoing community maintenance.