omnipay/sagepay

The package has strong consumer documentation, tests, release notes, and MIT licensing, backed by an organization-owned repository. Its small dependency footprint and clean workflow audit help, but the project shows little recent activity.

Latest 4.1.2

Packagist

55%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has 26 releases over about 13 years, but none in the last 12 months and its latest release was over two years ago. This materially raises maintenance and abandonment concerns.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. Combined with no registry releases in the last 12 months, this is a meaningful maintenance concern.

Repo issue activity

There were no new or closed issues or pull requests in the last month, while 25 issues remain open. This suggests limited recent project responsiveness.

Repo tooling

Composer is used for builds, but no security scanning tools were detected. The missing scanning is a hygiene gap, not evidence that the package is unsafe by itself.

Security policy

The repository has no published security policy, reducing transparency about vulnerability reporting and response expectations for a payment integration.