plutopay/plutopay-php

Usable with caveats: the package is actively published and backed by an organization, but it is very young, has only two releases, and recent repository work is limited to one contributor. The absence of tests and a security policy adds maintenance risk for a payments SDK.

Latest v0.1.1

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

A substantial README and changelog are present, and the repository uses GitHub Releases, but neither the package nor repository contains tests. For a payments SDK, that missing validation is a meaningful maintenance gap.

Release history

The package is only 65 days old and has two releases, with about 66 days between releases. This provides limited evidence of long-term maintenance or release consistency.

Repo bus factor

All two recent commits came from one contributor, concentrating maintenance responsibility. Organization backing partly offsets the risk because the project can potentially hand work to another maintainer.

Repo commit activity

Only two commits were recorded in the last three months, with one active maintainer. Recent work exists, but the pace offers limited evidence of sustained maintenance.

Repo issue activity

There are no open issues or pull requests and no recent issue or pull-request activity. This does not show unresolved problems, but it also provides little evidence of community review.