riverslei/payment

The project is established, clearly licensed, and documented for consumers. Its lack of a security policy and scanning leaves maintenance safeguards unclear.

Latest v5.1.0

Packagist

53%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has 45 releases since June 2016, but its latest registry release was over six years ago and it had no releases in the last 12 months. This materially raises staleness risk despite its historically regular release cadence.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, following a last push in December 2022. That prolonged lack of observed development is the main abandonment concern, though the repository is not archived.

Repo issue activity

There are 33 open issues and 8 open pull requests, but no new or closed issues or pull requests in the last month. This suggests unresolved work without visible recent triage.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. For a payment SDK, the missing automated security checks reduce transparency and maintenance assurance.

Security policy

The repository has no security policy. For software handling payment integrations, the absence of a documented vulnerability-reporting process is a meaningful transparency gap.