ertiz/omnipay-payu

The package is clearly licensed, includes a consumer README, and has a small, understandable dependency profile. Its source has no security policy or scanning, while maintenance activity has been absent for over nine years.

Latest 1.1

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases were published, both in January 2017, and none appeared in the following nine years. This strongly indicates abandonment risk for a dependency.

Repo commit activity

There were zero commits and zero active maintainers in the last three months, consistent with the release history showing no activity for over nine years. This is strong evidence of abandonment risk.

Project backing

The repository is owned by a user account rather than an organization. This offers no demonstrated institutional backing, but ownership type alone is not evidence of poor health.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. For a payment gateway integration, that missing security hygiene modestly lowers confidence.

Repository archived

The repository is not marked archived, but its last push was in January 2017; the non-archived status does not compensate for the observed dormancy.