kraz/read-model

kraz/read-model 1.3.0 appears usable and actively developed, with 12 releases over 116 days, a stable major version, recent repository pushes, repository tests, clear licensing, low runtime dependency count, and no deprecation or dangerous workflow findings. Adoption carries moderate risk because the project is young, all 10 recent commits come from one contributor, the repository has no security scanning or security policy, GitHub Actions permissions are not explicitly restricted, and the repository has no observed community activity or popularity. Overall, it is a reasonable dependency for teams comfortable with a small, single-maintainer project, but it warrants monitoring and possibly an internal review before critical use.

Latest 1.3.0

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access. This is a real continuity concern for a user-owned project because publishing and maintenance capacity are concentrated in one person.

Project backing

The repository is owned by an individual user rather than an organization, so there is no organizational backing to offset the concentrated maintainer and commit activity.

Release history

The package is young at 116 days but has 12 releases, all within the last 12 months, with a median interval of about 23 hours; this shows active iteration, though it provides limited evidence of long-term stability.

Repo bus factor

One contributor made all 10 commits in the last 3 months, producing a complete concentration of recent development in a single maintainer and creating a meaningful bus-factor risk.

Repo issue activity

There are no open issues or pull requests and no issue or pull-request activity in the last month. This does not prove abandonment, but it provides no evidence of an active user or contributor community.