craftcms/commerce-eway

Organization backing, a matching repository, and a security policy provide useful transparency. The small dependency set is reasonable, but workflow references are not pinned and repository security scanning is absent.

Latest 4.1.1

Packagist

67%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

100

Health Score Breakdown

Release history

The package has 12 releases since 2018, but none in the last 12 months and the latest release was about 19 months ago. This is meaningful maintenance concern despite an established release history.

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with the older latest release, this indicates slowed maintenance.

Repo issue activity

There are two open issues and one open pull request, with no issue or pull request activity in the last month. This is a mild sign of limited current attention.

Repo popularity

The repository has four stars and one fork, indicating limited community adoption, though popularity is supporting evidence rather than a health verdict.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest transparency and maintenance gap.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Pixel & Tonic

Direct Dependencies

Dependency	Last Release	Score
craftcms/cms Version ^4.0.0-RC3\|^5.0	—	—
omnipay/eway Version ~3.0	—	—
craftcms/commerce Version ^4.0.0-RC1\|^5.0	—	—
craftcms/commerce-omnipay Version ^4.1.0	—	—