80h4ck/tp5-auth

Clear licensing, a useful README, and no install-time scripts improve transparency and reduce setup risk. Long-term support remains uncertain because the sole maintainer has not released or updated the project for about eight years.

Latest 1.0.0

Packagist

34%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had only one release, published about 8 years and 8 months ago, with no releases in the last 12 months. This is strong evidence of abandonment risk despite the stable 1.0.0 version.

Repo commit activity

The repository recorded no commits and no active maintainers in the last 3 months, consistent with the package's long release gap. This materially weakens confidence in ongoing maintenance.

Maintainers

Only one registry account has publish access. That is a thin publishing base and increases continuity risk, although repository activity—not access records—is the stronger maintenance evidence here.

Repo tooling

Composer build tooling is present, but no security-scanning tooling was detected. This is a modest hygiene concern rather than evidence that the release is unsafe.

Repository archived

The repository is not archived, which is a positive counter-signal, although its last push was about 8 years and 10 months ago and therefore does not offset the inactivity evidence.