vocolboy/php-emv-qrcode

Clear documentation, tests, licensing, and a small runtime dependency footprint support adoption. Limited recent project activity and absent security practices increase the risk of relying on future fixes.

Latest 2.2.1

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The package and repository are owned by the same individual account. This is consistent ownership, but it does not provide the additional organizational backing that can broaden maintenance capacity.

Release history

The package has 7 releases over about 3 years, but none in the last 12 months; the latest release was about 14 months ago. This indicates a real maintenance concern, though the project has an established release history.

Repo commit activity

There were no commits and no active maintainers in the last 3 months. Combined with no registry releases in the last year, this points to currently quiet maintenance.

Repo popularity

The repository has only 1 star, fork, and watcher. Popularity is supporting evidence rather than a verdict, but this provides little evidence of a broad support community.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. That leaves an avoidable transparency and maintenance gap for a package handling payment QR data.