kanazaca/counter-cache

Release historydanger

The package has only two releases, with the latest published in October 2016 and none in the last 12 months. This long release gap 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. Combined with the old last push, this is direct evidence that development has stopped or nearly stopped.

Maintainerscaution

Only one registry maintainer is listed, so publishing continuity depends on a single person. The linked repository is also owned by an individual rather than an organization, offering no visible organizational redundancy.

Project backingcaution

The registry namespace and repository are both owned by the same individual account, with no organizational backing shown. That is consistent ownership but provides limited evidence of maintenance capacity.

Repo issue activitycaution

There is one open issue, but no new or closed issues and no pull-request activity in the last month. This suggests little current support activity and adds to the maintenance concern.