Package Health

phpviet/omnipay-momo

Documentation, tests, and a matching source repository provide useful transparency. However, the project has seen no release or commit activity since August 2019, and it lacks a security policy and scanning setup.

Latest 1.0.3PackagistPackagist

44%

Total Score

Maintainer Stability
Maintainer Stability
Assesses the consistency and reliability of package maintainers

50

Dependencies
Dependencies
Evaluates the health and security of package dependencies

100

Maturity
Maturity
Indicates package age, release frequency, and adoption metrics

75

Supply Chain
Supply Chain
Evaluates supply chain security practices and risks

75

Health Score Breakdown

Release historydanger

The latest release was published in August 2019, with no releases in the last 12 months; this is a substantial abandonment concern for a payment integration library.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months; combined with the last push in 2019, this strongly increases abandonment risk.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are configured, leaving a modest transparency and maintenance gap.

Repository archivedcaution

The repository is not archived, but its last push was in August 2019, so the unarchived status does not compensate for the prolonged inactivity.

Security policycaution

The repository has no security policy, which weakens vulnerability-reporting transparency for payment-related code.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Vuong Xuong Minh

Direct Dependencies

DependencyLast ReleaseScore
omnipay/common
Version ^3.0
—
—

Weekly Downloads

Info

Last Published
7 years ago
Created
7 years ago

Are You Affected?

Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.

Free. No credit card required.

Aikido Platform