uocnv/momo-payment

The README and release notes give consumers a clear starting point. MIT licensing and a repository that matches the package reduce transparency concerns, while the lone maintainer and absent security tooling leave limited operational depth.

Latest 1.0.2

Packagist

52%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had three releases, but its latest release was about 18 months ago and there were no releases in the last 12 months. This indicates stalled maintenance for a payment integration.

Repo commit activity

The repository recorded no commits or active maintainers in the last 3 months, and its last push was about 18 months ago. That leaves little evidence of ongoing maintenance.

Maintainers

One registry maintainer creates a thin publishing and support base. The repository is user-owned rather than organization-owned, so there is no provided backing signal to offset that concentration.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. For a payment package, this is a meaningful process gap, though it does not prove the code is unsafe.

Security policy

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This matters more for a package handling payment flows.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Nguyen Van Uoc

Direct Dependencies

Dependency	Last Release	Score
monolog/monolog Version *	—	—
illuminate/support Version ~5.0\|^6.0\|^7.0\|^8.0\|^9.0\|^10.0\|^11.0	—	—
phpseclib/phpseclib Version ^2	—	—
bramus/monolog-colored-line-formatter Version ^3.0	—	—