omnipay/cardsave

The MIT license, included tests, stable version, and small dependency surface make the package transparent and straightforward to inspect. However, its maintenance and security posture are dated, with no recent repository activity or security policy.

Latest 2.1.2

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published in December 2014, with no releases in the last 12 months. That long gap is strong evidence of abandonment for a payment integration.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package having been inactive for years.

Repo issue activity

There were no new or closed issues or pull requests in the last month. With the equally inactive commit history, this provides no evidence of ongoing maintenance.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. This is a hygiene gap, though it is less significant than the package's prolonged inactivity.

Security policy

The linked repository has no security policy, reducing transparency for reporting and handling vulnerabilities. This compounds the package's long maintenance gap.