aait/payex-wordpress-api

The MIT license and simple Composer setup are clear, but documentation is sparse and no security tooling is present. Pinning this release leaves you exposed to an unmaintained integration.

Latest v1.0.1

Packagist

32%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases exist, with the latest published in May 2017 and none in the last 12 months. This indicates a long-standing lack of maintenance for a payments integration.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no recent updates.

Repo package mention

The repository name does not match the package name and its README does not mention the package, so the source-package relationship is not clearly demonstrated.

Package file tree

The artifact contains only four files and a single source file, providing little visible project structure for a payments client. The small tree is not inherently unsafe, but it limits transparency.

Package scaffolding

A README is present, and missing tests and changelog files are normal for a published PHP artifact. However, the README is only 630 characters and leaves its examples marked TODO, limiting consumer guidance.