hassankhan/config

The project has strong release notes, repository tests, and a matching source repository. Its small dependency footprint and clean workflow audit help, but no commits or issue closures for about 19 months limits confidence.

Latest 3.2.0

Packagist

67%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The registry namespace and repository are owned by the same individual, so the package has direct ownership alignment but not organization-level backing. This provides accountability without a broad maintainer capacity.

Release history

This is a mature package first released in 2015 with 31 releases, but it has had no registry release in the last 12 months. The long history partly offsets the recent release gap.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, indicating maintenance has stalled for about 19 months since the last recorded push.

Repo issue activity

There are 16 open issues and 7 open pull requests, but no issues or pull requests were closed in the last month. This is a maintenance warning when combined with the inactive commit history.

Repo tooling

Composer is used as the build tool, which fits the package ecosystem, but no security scanning tools were detected. The missing scanning is a modest transparency gap rather than evidence of abandonment.