getresponse/magento2

This is a usable, established package with nearly nine years of release history, 89 releases, 12 releases in the last 12 months, a stable non-prerelease version, an active non-archived organization-owned repository, and a clear OSL-3.0 license declaration. However, the repository shows no commits or active maintainers in the last 3 months, has no tests, no security scanning, and no security policy; these are meaningful transparency and maintenance concerns despite the very recent release and repository push. Overall, it is suitable for consideration but should be adopted with monitoring and validation of ongoing maintenance.

Latest 21.4.1

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

A README and changelog are present, and the repository uses GitHub Releases, which provide useful release documentation. Neither the artifact nor repository contains tests, leaving maintenance and regression coverage less transparent.

Repo commit activity

The repository recorded zero commits and zero active maintainers over the last 3 months, a significant maintenance concern. The recent package release and repository push partly offset this, but they do not establish sustained source development.

Repo tooling

Composer is used as a build tool, providing basic project tooling, but no security scanning tools are configured, leaving a security-hygiene gap.

Security policy

No repository security policy was found, reducing transparency about vulnerability reporting and maintainer response procedures.