Package Health/zwiebelmettwurst/omnipay-asiapay

zwiebelmettwurst/omnipay-asiapay

Risky to adopt without taking on maintenance risk: the package has had no release or repository commits for about 2 years and 4 months. It is not deprecated or archived, but the single-person project has little evidence of ongoing support.

Latest 1.4

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published about 2 years and 4 months ago, with no releases in the last 12 months. Five releases clustered within roughly a day show an initial publication burst but no continuing maintenance.

Repo commit activity

The repository recorded zero commits and zero active maintainers over the last three months. Combined with the old latest release, this is strong evidence that ongoing maintenance is absent.

Maintainers

Only one registry account has publish access. That is a limited publishing base for a user-owned project and increases continuity risk if the maintainer becomes unavailable.

Project backing

The repository is owned by the same individual account as the registry namespace, confirming consistent ownership but no organizational backing. This leaves the project dependent on a single maintainer.

Repo issue activity

There were no new issues or pull requests in the last month and no merged pull requests. The unknown open-issues count prevents stronger conclusions, but the observed lack of collaboration does not provide maintenance reassurance.