lifo/php-daemon

Usable with caveats: the repository is maintained enough to remain available and the release is clearly packaged, but the registry has had no release in more than three years and recent commit activity is absent. Treat it as a stable legacy dependency and verify compatibility before adopting it.

Latest v2.0.1

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

One registry publishing account is associated with the package. Because the repository is user-owned rather than organization-backed, this leaves a relatively thin maintainer base and increases continuity risk.

Release history

Only three releases exist, with no release in more than three years and a median interval of about two years and six months. This is a meaningful maintenance and compatibility concern for a library dependency.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the long registry release gap, this points to slow maintenance and raises the chance that compatibility issues will remain unresolved.

Repo tooling

Composer build tooling is present, but no security-scanning tooling was detected. This is a transparency and maintenance gap, though it is not severe enough on its own to make the package unfit.

Security policy

The repository has no documented security policy, leaving no clear public process for reporting or handling vulnerabilities.