gopay/payments-sdk-php

Documentation, tests, a changelog, and a clear MIT license make the release straightforward to evaluate and use. Unpinned workflow actions and no repository security policy weaken build transparency, while recent inactivity suggests maintenance should be watched.

Latest 1.11.1

Packagist

72%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

There were no commits and no active maintainers in the last 3 months, indicating a recent maintenance pause that raises abandonment and responsiveness concerns.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected, leaving less automated coverage for dependency and source risks.

Security policy

The repository has no security policy, which reduces transparency about vulnerability reporting and response expectations for a payment SDK.

Workflow audit

The single workflow was fully analyzed with no dangerous sinks or audit findings, but both action references are unpinned, so their executed code is not fixed to reviewed revisions.