chriswest101/paynow

The package has clear usage documentation, tests in the repository, and a source tree that matches the package. Its single-person ownership, sparse release history, and lack of recent commits make long-term maintenance less certain.

Latest v2.0

Packagist

65%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publish access, and project backing identifies an individual owner rather than an organization. This leaves limited visible maintainer redundancy if that person stops supporting the project.

Release history

The package has existed for about 5 years and 10 months, but only 5 releases overall, with 1 release in the last year and a median interval of about 20 months. This indicates a slow maintenance cadence, though the release in the last year is evidence the project is not abandoned.

Repo commit activity

The repository recorded 0 commits and 0 active maintainers in the past 3 months. The recent release and repository push partly offset this, but the current development pace is still quiet.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. For a payment QR-code library, that is a modest transparency and maintenance gap, not evidence of unsafe behavior by itself.

Security policy

The repository has no security policy. That reduces clarity about how vulnerabilities should be reported and handled, especially for a package involved in payment workflows.