kraz/read-model-doctrine

This is a usable and reasonably transparent release with an MIT license, a matching repository, documented source structure, repository tests, recent release activity, and no deprecation or archival indicators. The main concerns are that the project is young at 116 days, all three commits in the last three months came from one contributor, the repository has no security scanning or security policy, and its workflow does not declare top-level token permissions. These issues increase maintenance and operational risk, but the recent releases, active repository, stable 1.3.0 version, and substantial test suite keep it in the cautionary rather than unhealthy range.

Latest 1.3.0

Packagist

72%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The repository is owned by a User account rather than an organization, so there is no provided organizational backing to offset the concentrated maintainer activity.

Repo bus factor

One contributor produced 100% of the recent commits, creating a meaningful continuity and abandonment risk for this user-owned project.

Repo commit activity

There were three commits in the last three months from one active maintainer. Recent activity is positive, but the low volume and single-person activity limit evidence of sustained maintenance capacity.

Repo popularity

The repository has zero stars, forks, and watchers. This is weak supporting evidence for adoption and external review, but popularity alone is not decisive for a small package.

Repo tooling

Composer build tooling is present, but no security scanning tools are configured. The missing scanning reduces assurance around ongoing dependency and code hygiene.