diasfs/graphql-php-resolvers

Release historydanger

The package has made only two releases, with no releases in about seven years; its last recorded release was in March 2019. This is strong evidence of abandonment risk despite the short initial 28-day release interval.

Repo commit activitydanger

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

Maintainerscaution

Only one registry account has publishing access. That can be normal for a personal project, but here it offers no visible redundancy alongside the inactive repository.

Repo issue activitycaution

There is one open issue, with no issues or pull requests created or closed in the last month. The small issue count is not itself severe, but the lack of recent response adds to the maintenance concern.

Repo popularitycaution

The repository has one star, zero forks, and one watcher, providing little evidence of an active user or contributor community to compensate for the inactive maintainer.