Package Health/yasinkuyu/omnipay-paratika

yasinkuyu/omnipay-paratika

The MIT license, focused dependency set, and matching source repository support straightforward adoption. A single maintainer, no recent commits, and no security policy leave meaningful long-term maintenance risk.

Latest 2.0.3

Packagist

55%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was in January 2019, with no releases in the last 12 months. That long gap is a substantial maintenance concern for a payment gateway, despite four historical releases.

Repo commit activity

There were no commits or active maintainers in the last three months. Combined with the old latest release, this is strong evidence that maintenance has stalled.

Maintainers

Only one registry maintainer is listed, leaving a thin publishing base. The repository is user-owned rather than organization-backed, so there is no provided evidence of broader operational support to offset that risk.

Project backing

The registry namespace and repository are both owned by the same user, which supports ownership continuity, but the provided data shows no organization backing.

Repo tooling

Composer is used as the build tool, but no security scanning tools are configured. The missing scanning is a modest transparency and maintenance gap rather than evidence that the package is unsafe.