contestio/magento2

The repository has no commits or active maintainers in the last three months, and it lacks a security policy. Frequent releases and organization backing provide some maintenance evidence, but the repository-to-package name mismatch makes ownership less clear.

Latest 1.2.12

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

The repository recorded zero commits and zero active maintainers during the last three months. That is a meaningful maintenance concern, especially alongside the absence of recent issue or pull-request activity.

Repo issue activity

There were no new or closed issues and no new or merged pull requests in the last month, with no open issues or pull requests. This indicates little visible community or maintainer activity, though the package may be stable and organization-backed.

Repo package mention

The repository name does not match the package name, and no README package mention was available. This weakens confidence that the linked repository directly documents this package, although a subpackage or plugin repository can use a different name.

Repo tooling

Composer is used as a build tool, which fits this Magento package, but no security scanning tools are configured. The missing scanning is a hygiene gap rather than evidence of unsafe code.

Security policy

The repository has no security policy. That reduces vulnerability-reporting transparency, although it is not by itself evidence that the package is unmaintained.