palacios/framework

This is a very young, pre-1.0 package with only two releases over 2 days, so its long-term maintenance, API stability, and operational maturity are not yet established. The linked repository is active, correctly associated with the package, unarchived, and includes substantial documentation, tests, a changelog, a license, security policy, CI workflow, and read-only workflow permissions. However, all 10 recent commits come from one contributor, the repository has no observed popularity or issue activity yet, and no security-scanning tooling is reported. It is usable for experimentation or closely monitored adoption, but should be treated as a higher-change-risk dependency rather than a mature production foundation.

Latest v0.1.1

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

100

Health Score Breakdown

Project backing

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

Release history

The package is only 2 days old and has 2 releases, so there is too little history to demonstrate sustained maintenance or mature release practices. The roughly 2-day median release interval shows early activity but not durability.

Repo bus factor

One contributor made all 10 recent commits, producing a 100% top-contributor share and a significant continuity risk for a user-owned project.

Repo popularity

The repository has 0 stars, forks, and watchers. For a package only 2 days old this is not evidence of abandonment, but it provides no external adoption or maturity support yet.

Repo tooling

Composer build tooling is present, but no security-scanning tools are reported. The missing scanning layer is a genuine transparency and maintenance gap for a framework, though it is not by itself evidence of unsafe code.