beeeye/lumen-graphql

The single maintainer and one-star repository leave little visible support. A clear README, MIT declaration, and no install-time scripts improve transparency, but do not offset the limited project activity.

Latest 1.0.0

Packagist

40%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

This package has only one release, published about seven years ago, with no releases in the last 12 months. That is strong evidence of abandonment risk, although the registry does not mark it deprecated.

Maintainers

Only one account has registry publishing access, leaving limited visible publishing continuity. This is a concern for a project that also shows no recent release activity, though access records do not prove who actively maintains it.

Repo popularity

The repository has one star, no forks, and no watchers, providing little supporting evidence of an active user or contributor community. Popularity is only supporting evidence, so this reinforces rather than determines the result.

Repository archived

The linked repository is not archived, which is a meaningful positive. However, its last push was about seven years ago, so this does not compensate for the lack of current maintenance shown by the release history.

Security policy

The linked repository has no security policy, reducing transparency for reporting and handling vulnerabilities. This is a secondary concern alongside the much stronger evidence of inactivity.