200mph/myxa-framework

Documentation, tests, licensing, and release notes are in place, with a small runtime dependency set. The project has had no commits in three months, has one registry maintainer, no security policy, and weak workflow pinning, so long-term maintenance deserves caution.

Latest 1.1.0

Packagist

55%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. For a framework released only a few months ago, that is a meaningful maintenance concern.

Project backing

The repository owner is an individual user rather than an organization, so the single registry maintainer provides limited visible ownership redundancy.

Release history

The package has 11 releases in its first 165 days, but the latest release was about four months ago, indicating an early burst followed by a meaningful pause.

Repo popularity

The repository has zero stars, forks, and watchers. This is weak supporting evidence for maturity, but popularity alone does not establish that the package is unsafe to depend on.

Repo tooling

Composer build tooling is present, but no security-scanning tool was detected. This is a transparency and hygiene gap rather than evidence of abandonment by itself.