omnipay/buckaroo

The MIT license, included tests, clear README, and small dependency footprint support straightforward adoption. However, the package has seen no release for over nine years and the repository has had no recent commit or issue activity, so maintenance risk is significant.

Latest v2.2.0

Packagist

54%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published in June 2017, with no releases in the past 12 months. This long release gap is a substantial maintenance concern for a payment integration.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the past three months, consistent with a project that is no longer actively maintained.

Repo issue activity

There were no new or closed issues or pull requests in the past month, while four issues and three pull requests remain open. This suggests limited ongoing project attention.

Repo tooling

Composer is used as the build tool, but no security scanning tools were detected. The missing scanning is a modest transparency and hygiene gap, not evidence of unsafe code.

Security policy

The repository has no security policy. That weakens vulnerability-reporting transparency, though it is less significant than the package's prolonged inactivity.