Package Health/microweber-packages/omnipay-momo-mtn

microweber-packages/omnipay-momo-mtn

The package has clear documentation, tests, and a matching organization-owned repository. Its MIT declaration, small runtime dependency surface, and limited install-time behavior are reassuring, though the project offers little evidence of broader security practice.

Latest 0.2

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases were published, both about one hour and forty minutes apart on the same day, with no later release over nearly a year. This gives little evidence of sustained release maintenance.

Repo commit activity

There were no commits and no active maintainers in the last three months. For a payment integration, this is meaningful evidence of limited ongoing maintenance capacity.

Repo tooling

Composer build tooling is present, but no security-scanning tool was detected. This is a modest transparency and maintenance gap rather than a severe risk.

Security policy

The repository has no security policy. That weakens disclosure transparency, especially for a package handling payment integrations, but does not by itself make the release unfit.

Version stability

Version 0.2 is not a stable major release, so the API may still change. It is not marked as a prerelease, which partly offsets the maturity concern.