jbboehr/yumemi

This is a promising but very young pre-1.0 package with strong repository evidence of active development: 370 commits in the last three months, a current non-archived repository, extensive documentation and source scaffolding, a changelog, and repository tests despite tests not being included in the artifact. The main adoption risks are its 24-day history, v0.2 stability contract, single maintainer and sole contributor, zero observed popularity or issue activity, and lack of a security policy. It is not deprecated, has a clear AGPL license, uses read-only workflow permissions, and shows no analyzed dangerous workflow patterns, so it appears usable with normal caution around API stability and maintainer concentration.

Latest v0.2.0

Packagist

70%

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, although repository activity shows that the maintainer is currently active.

Project backing

The repository is owned by the individual user jbboehr rather than an organization, so there is no observed organizational backing to offset the single-maintainer and single-contributor risks.

Release history

The package is only 24 days old with three releases and a median release interval of 12.4008 days (about 12 days), so there is not yet enough history to establish long-term maintenance reliability.

Repo bus factor

All 370 recent commits came from one contributor, giving the project a complete contributor concentration and creating a significant continuity risk without organizational backing.

Repo issue activity

There are no open issues or pull requests and no issue or pull-request activity in the last month. This is ambiguous for a new package and is weaker evidence than a demonstrated maintenance backlog or resolution history.