Package Health/getresponse/magento2-module

getresponse/magento2-module

Usable with caveats: it has a long release history, regular recent releases, and is backed by an active organization-owned repository. However, the repository and package contain only two files, with no tests, documentation, changelog, recent commits, or security policy, making transparency and ongoing maintenance harder to verify.

Latest 2.4.1

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package file tree

Both the package and linked repository contain only .gitignore and composer.json. Such a minimal tree leaves no implementation, test, or documentation evidence to inspect and substantially limits transparency.

Package scaffolding

Neither the artifact nor repository has a README, tests, or changelog. GitHub Releases provide some release transparency, but the lack of tests and documentation remains a meaningful maintenance and adoption gap.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. This conflicts with the recent registry release cadence and leaves current source maintenance difficult to verify.

Repo issue activity

There are five open issues but no new or closed issues and no pull-request activity in the last month. This provides little evidence of current issue response or collaborative maintenance.

Repo popularity

The repository has zero stars and one fork, indicating very limited visible adoption. Popularity is only supporting evidence, but these numbers provide no community-maintenance cushion.