wazum/solr-eager-flush

This is a promising but still young package with strong evidence of active development: eight stable releases in 98 days, recent repository activity, a substantial test suite in the repository, clear documentation, changelog, licensing, and no deprecation or archive status. The main concerns are that all 24 recent commits come from one contributor, the repository has no security policy, and its GitHub Actions workflows declare no top-level token permissions. These issues reduce resilience and transparency, but the package appears actively maintained and technically structured enough to remain usable for developers who can accept the single-maintainer risk.

Latest 1.6.0

Packagist

72%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one account has registry publish access, but registry access reflects publishing permissions rather than actual maintenance capacity; repository activity confirms that this contributor is active, while the single-person project remains a resilience concern considered under repository bus factor.

Project backing

The repository is owned by a personal user account rather than an organization, so there is no visible organizational maintenance backing to offset the concentrated contributor base.

Repo bus factor

One contributor made all 24 commits in the last three months, giving the project a complete single-contributor concentration and creating a meaningful continuity risk.

Repo issue activity

There is one newly opened issue in the last month and no issues or pull requests were closed, showing some engagement but limited evidence of issue-resolution throughput.

Repo popularity

The repository has only 1 star, 0 forks, and 0 watchers, indicating limited external adoption or visibility. Popularity is supporting evidence rather than a health verdict, so this is only a mild concern.