wwwision/graphql

Maintainerscaution

Only one account has registry publishing access. That can be adequate for a small package, but combined with the lack of recent activity it increases continuity and abandonment risk.

Project backingcaution

The repository is owned by an individual rather than an organization, so the single registry maintainer is not explained by organization-backed publishing capacity. The package and repository are nevertheless clearly linked by the README mention.

Release historycaution

The package has existed since 2016 with 30 releases, but it has had no registry release in the last two and a half years, which is a meaningful maintenance concern for a framework integration.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months, consistent with a project that has been inactive since its last release about two and a half years ago.

Repo issue activitycaution

There are no open issues or pull requests, but there is also no recent issue or pull-request activity. This is neutral evidence rather than proof of active maintenance.