Package Health/eventcollect/omnipay-eventcollect

eventcollect/omnipay-eventcollect

This is a generally healthy package to depend on: it has a stable 3.2.0 release, a long release history, a current non-archived repository, organization backing, matching repository references, a clear MIT license, packaged tests, and no install-time lifecycle scripts. The main concerns are that only one release occurred in the last 12 months, repository commit activity shows no commits or active maintainers in the last 3 months despite three merged pull requests, and the repository has no security scanning or security policy. Its very low popularity is a consideration for ecosystem support, but not by itself evidence of poor maintenance or abandonment.

Latest 3.2.0

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has existed for about 5 years with 15 releases, but only one release in the last 12 months indicates slower recent release cadence than its historical median interval of about 21 days.

Repo commit activity

No commits and no active maintainers were recorded in the last 3 months. The recent merged pull requests provide some compensating evidence, but the direct commit-maintenance signal remains weak.

Repo popularity

The repository has only 1 star, 0 forks, and 1 watcher, indicating limited external adoption and a potentially small support community; this is supporting caution rather than a standalone health verdict.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected, leaving a repository security-hygiene gap.

Security policy

The repository has no SECURITY.md or other detected security policy, reducing transparency about vulnerability reporting and response.