jaysson/omnipay-payubiz

The MIT license, focused dependency set, and clear README make the package straightforward to evaluate and adopt. Its only release was published in 2016, with no recent issue activity and no security policy, leaving maintenance and support risk high.

Latest 1.0

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only one release, published about 10 years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk, though the repository is not archived.

Project backing

The repository is owned by an individual account rather than an organization, and the registry maintainer list contains one person. That is not inherently unhealthy, but it offers limited visible continuity for a long-stale package.

Repo issue activity

There is one open issue, but no new or closed issues and no pull requests in the last month. This supports the broader indication that the project is not actively maintained.

Repo popularity

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these values provide no community signal to offset the stale release history.

Repo tooling

The repository uses Composer, which is appropriate for this PHP package, but it has no security scanning tools. The missing scanning is a modest transparency and maintenance gap.