papihack/payexpresse-php-client

Release historydanger

The package has only two releases, with the latest published over six years ago and none in the last 12 months. This strongly raises abandonment risk despite the short early release interval.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with the last push being over five years ago. This is the strongest evidence of ongoing abandonment risk.

Repo popularitycaution

The repository has only 2 stars, 0 forks, and 1 watcher. Popularity is supporting evidence rather than a verdict, but these counts provide little evidence of a broad support community.

Repo toolingcaution

Composer is used for builds, but no security-scanning tooling is present. The missing scanner is a modest transparency gap, not a standalone reason to reject the package.

Security policycaution

The repository has no security policy, leaving no documented path for reporting vulnerabilities or coordinating fixes. This adds a maintenance and response gap for a payment API client.