leonardothibes/payu

The missing security policy and scanning, plus one-person ownership, reduce confidence in ongoing support. A README, MIT license, and extensive tests help consumers, but do not offset nearly 12 years without a release or nearly 11 years without repository updates.

Latest 0.8

Packagist

40%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was in December 2014, with no releases in the last 12 months and a package age of over 12 years. This is strong evidence that maintenance has stopped.

Repo commit activity

The repository had zero commits and zero active maintainers in the last three months. Combined with the old last push, this is strong abandonment evidence.

Maintainers

Only one registry maintainer is listed, limiting visible publishing redundancy. The linked repository is also owned by an individual, so there is no organizational backing shown to compensate for that narrow base.

Repo issue activity

There were no new or closed issues or pull requests in the last month, and three issues remain open. This indicates no current maintenance activity.

Repo tooling

The project uses Make and Composer, showing basic build structure, but it has no security scanning tools. That leaves an important maintenance and review gap for a payment-integration library.