ashishpatel0720/kisanmitra

Release historydanger

Only two releases exist, with none in the last 12 months and the latest published about six years ago. This strongly raises abandonment risk despite the package not being deprecated.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months. Combined with the old latest release, this is strong evidence that maintenance has stalled.

Lifecycle scriptscaution

The package defines post-create, post-install, post-root-package-install, and post-update Composer scripts, so installation and updates execute project code and deserve extra review.

Project backingcaution

The repository is owned by an individual user rather than an organization. That offers less visible backing capacity, but ownership metadata alone does not establish abandonment.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month, while 18 pull requests remain open. This suggests limited recent project management activity.