leanpay/payment

Usable with caveats: it has regular releases, recent source changes, and two equally active contributors, but the package has no license and no tests or security policy. Confirm licensing and test coverage before making it a core dependency.

Latest 0.16.0

Packagist

68%

Total Score

Maintainer Stability

100

Dependencies

100

Maturity

Supply Chain

Health checks

License

No declared license or license file was found in the package or repository, leaving the terms for using this payment integration unclear.

Package scaffolding

The artifact includes release notes and the repository uses GitHub Releases, but neither contains tests or a conventional changelog. For a payment integration, the lack of visible automated tests is a meaningful maintenance gap.

Repo package mention

The repository name does not match the package name, and the collected README mention is null, so the repository-package relationship is not clearly demonstrated. This creates a transparency concern even though the mismatch could reflect a repository containing a related integration.

Repo tooling

Composer is used for builds, but no security scanning tool is configured. That weakens automated supply-chain hygiene without indicating abandonment by itself.

Security policy

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented for a payment-related package.