chapdel/auth

It has a clear MIT license, documentation, tests in the repository, and a security policy. The single release and no commits for about two and a half years leave maintenance and future compatibility uncertain, while the repository does not identify this package clearly.

Latest 1.0

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

100

Health Score Breakdown

Project backing

The registry namespace and repository owner match, so the source ownership is internally consistent. The owner is an individual account, offering less visible organizational backing.

Release history

Only one release exists, published about two and a half years ago, with no releases in the last 12 months. That provides little evidence of ongoing maintenance.

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with the single-release history, this is strong evidence that development has stalled.

Repo package mention

The repository name does not match the package name and its README does not mention the package. That makes the source relationship less clear and raises a risk that the repository is not the package's intended home.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest hygiene gap rather than evidence that the package cannot be maintained.