esas/cmsgate-epos-lib

The stable version, organization backing, and small dependency set reduce adoption friction. Missing tests, documentation, security scanning, and a security policy limit transparency and confidence in ongoing maintenance.

Latest v2.2.5

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The package contains no readme, tests, or changelog, although tests and changelogs are normally repository-level assets and their absence from a published PHP artifact is expected. The missing readme is still a minor transparency gap for an integration library.

Release history

The package has 51 releases since April 2020, but its latest release was over two years ago and it had no releases in the last 12 months. This is meaningful evidence of a slowing or stopped release process.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. Combined with no registry releases in the last year, this raises concern about current maintenance capacity.

Repo tooling

Composer is used as the build tool, which fits the package ecosystem, but no security scanning tool is configured. This is a hygiene and transparency gap rather than evidence that the package is unsafe.

Security policy

The linked repository has no security policy. For a payment integration library, the absence of a documented vulnerability-reporting path weakens maintenance transparency.