enessvg/laravel-paynet

This is a usable, well-scaffolded MIT-licensed Laravel payment SDK with tests, a changelog, a substantial README, a stable release line, no deprecation, no install-time scripts, and a repository that matches and documents the package. However, it is still young at 201 days old, has only one registry maintainer, very low repository adoption, no recorded commits or active maintainers in the last 3 months, no security scanning, and no security policy. The recent release and repository push are positive, but the lack of measured ongoing commit activity makes maintenance continuity uncertain; treat it as a reasonable dependency with heightened review and monitoring rather than a mature, low-risk foundation.

Latest v3.0.2

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one account has registry publish access, creating a limited publishing base; this is a genuine continuity concern because no organization backing is shown by the provided ownership data.

Project backing

The repository is owned by the individual user enessvg rather than an organization, so the single-maintainer concern is not compensated by demonstrated organizational backing.

Release history

The package is young at 201 days and has 11 releases, with a median interval of about 16 hours; this shows active publishing but provides limited evidence of long-term maintenance maturity.

Repo commit activity

The repository records 0 commits and 0 active maintainers over the last 3 months. Although the latest release and repository push are recent, the measured absence of ongoing commit activity leaves maintenance continuity uncertain.

Repo issue activity

There are no open issues or pull requests and no recent issue or pull-request activity; this is not inherently negative, but it provides little evidence of an active maintenance or user-support process.