fannypack/momo

The repository matches the package and includes a useful README, while the small codebase has limited dependency complexity. There is no security policy or automated security scanning, leaving little evidence of ongoing maintenance discipline.

Latest 1.01

Packagist

40%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases were published, with the latest in December 2019 and none in the last 12 months. This long release gap is strong evidence of abandonment risk for a library integrating a changing payment API.

Repo commit activity

The repository recorded no commits and no active maintainers in the last three months, consistent with a project that has not been actively maintained for several years. The non-archived status does not compensate for the lack of recent work.

License

Neither the package nor the linked repository contains a declared license or license file. That creates a material adoption and redistribution risk for an open-source dependency.

Repo tooling

Composer is used for the build, which fits the PHP package, but no security-scanning tools are configured. This provides limited evidence of maintenance and security quality.

Security policy

The repository has no security policy. This is a transparency gap for a library handling payment API credentials, although the absence alone does not show a security defect.