fillup/guzzle-services

The artifact is well structured, tested, documented, and clearly licensed, with a repository that matches the package. Its zero security tooling and very small community provide little additional assurance for future maintenance.

Latest 0.5.1

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no releases in the past 12 months, and its latest release was about 10 years ago. This is strong evidence of abandonment risk, although the package is not deprecated or archived.

Repo commit activity

There were no commits and no active maintainers in the past three months. Combined with the last push being about 10 years ago, this is strong evidence that maintenance has stopped.

Project backing

The repository is owned by a personal user account rather than an organization. This provides no visible organizational backing to offset the thin current maintenance evidence.

Repo popularity

The repository has zero stars and three forks, offering little evidence of a broad active user community. Popularity is only supporting evidence, so this reinforces rather than determines the abandonment concern.

Repo tooling

The repository uses Make and Composer, but no security scanning tools were detected. This is a meaningful hygiene gap, though it is less serious than the package's lack of current maintenance.