hjerichen/framework.graphql

Maintainerscaution

Only one registry account has publish access, which creates a thin publishing base. The matching repository owner and package mention provide some backing, but do not remove the single-maintainer continuity risk.

Project backingcaution

The registry namespace and repository owner match, but the owner is an individual account rather than an organization. This supports package identity while leaving limited organizational continuity evidence.

Release historycaution

Five releases over about 5 years, with a median interval of about 350 days and only one release in the last 12 months, indicate a slow maintenance cadence. The recent 0.4.0 release is positive but does not offset the limited history.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers during the last three months. The recent release is compensating evidence, but the short-term development pause still lowers maintenance confidence.

Repo issue activitycaution

There are no open issues or pull requests and no activity in the last month. With no reported backlog this is not negative by itself, but it provides little evidence of an engaged community.