yuxiaoyang/appnetpay

The MIT license and focused four-file package make the codebase straightforward to inspect and integrate. However, it has had no release or repository commit activity for over nine years, with one registry maintainer and no tests or security scanning.

Latest 1.0

Packagist

43%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only one release, published over nine years ago, with no releases in the last 12 months. This is strong evidence of abandonment for a payment integration.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the old last push, this indicates sustained abandonment risk.

Maintainers

Only one registry account has publish access. This is a thin publishing base and increases continuity risk, especially alongside the absence of recent releases.

Package file tree

The artifact contains only four files, including the manifest, README, and two source files. That compact structure is inspectable, but it provides little evidence of broader project maturity.

Project backing

The repository is owned by an individual account rather than an organization, and no broader project backing is shown. That makes the single-maintainer continuity concern more significant.