gillix/framework

The stable API and clear README make integration easier. A single maintainer, no recent commit activity, and no security policy leave less support and transparency if problems arise.

Latest 1.2.2

Packagist

58%

Total Score

Maintainer Stability

Dependencies

Maturity

Supply Chain

Health Score Breakdown

Dependency profile

The package has 11 runtime dependencies and no development dependencies, creating a meaningful dependency surface for a framework. The signal does not show that any individual dependency is unsafe, so this is a moderate maintenance concern rather than a severe one.

Maintainers

Only one registry account has publish access. Because the repository is owned by an individual rather than an organization, the narrow publishing base offers limited continuity if that maintainer becomes unavailable.

Project backing

The repository is owned by a user account, not an organization, so there is no observed organizational backing to compensate for the narrow maintainer base or stalled activity.

Release history

The package has 121 releases and a long history, but it has had no releases in the last 12 months; the latest release was about 16 months ago. This points to slowing maintenance.

Repo commit activity

The repository had zero commits and zero active maintainers in the last three months, consistent with the absence of releases in the last year. This materially raises abandonment and support risk.