congmingpay/php-sdk

The package includes a README, tests, a declared MIT license, and no install-time scripts. Its recent release activity is encouraging, but no security policy, zero repository engagement, and one active contributor limit confidence in long-term maintenance.

Latest v3.1.6

Packagist

65%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo bus factor

One contributor performed all commits in the last three months, creating a high concentration risk. The repository is user-owned rather than organization-owned, so no organizational handoff is shown to compensate for it.

Repo commit activity

Only one commit was recorded in the last three months, from one active maintainer. The recent push is positive, but the very small activity sample gives 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 is not proof of neglect, but it leaves little evidence of community review or support.

Repo popularity

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but the absence of any external adoption provides little independent validation for this young package.

Repo tooling

Composer is used for builds, which fits the ecosystem, but no security scanning tooling was detected. That is a meaningful transparency gap for a payment SDK, though it is not severe on its own.