alexaandrov/laravel-graphql-client

Release historydanger

The latest release was published in August 2019, and there have been no releases in the last 12 months. A five-release history over only a few days followed by roughly seven years of silence is a major maintenance concern.

Repo commit activitydanger

The repository recorded 0 commits and 0 active maintainers in the last three months, consistent with the long release gap and indicating no observed ongoing maintenance.

Maintainerscaution

One registry account has publishing access, and the repository is owned by an individual rather than an organization. This is not inherently unsafe, but it leaves little visible redundancy if the maintainer becomes unavailable.

Project backingcaution

The package and repository are consistently owned by the same individual account, which supports provenance, but there is no organizational backing shown to compensate for the single-maintainer structure.

Repo popularitycaution

The repository has 12 stars and 5 forks, showing limited adoption. Popularity is only supporting evidence, but the small audience provides little evidence of a broad maintenance community.