cjweber/laravel-test-graphql-client

Release historydanger

The package has four releases over about six years, but none in roughly four years; this is the strongest sign that maintenance has stopped.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with the release gap and indicating no recent maintenance capacity.

Project backingcaution

The package and repository are owned by the same individual account, so the project identity is clear, but there is no organizational backing to compensate for the thin maintenance base.

Repo popularitycaution

The repository has only four stars and four forks. Low popularity is supporting evidence rather than a verdict, but it provides little evidence of broad community support.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected; this is a modest transparency and monitoring gap.