verbb/cloner

Usable with caveats: it is a mature, licensed plugin backed by an organization and has a current stable release. However, repository commits and issue activity have been absent for three months, and the project has no tests or automated security scanning.

Latest 3.0.3

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

100

Health Score Breakdown

Package scaffolding

The package includes a README and changelog, but neither the artifact nor repository contains tests. For a plugin that changes content-management behavior, the lack of visible tests is a meaningful maintenance and regression concern.

Release history

The package has existed for about 7 years and has 23 releases, but only one release was published in the last 12 months. Its long history and latest release partly compensate for the slower recent cadence, but maintenance appears less active.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. The current release and recent repository push provide some compensation, but the lack of sustained commit activity raises abandonment and maintenance concerns.

Repo issue activity

There are three open issues, but no issues or pull requests were opened or closed in the last month. This suggests limited recent project interaction, although the small issue backlog is not severe by itself.

Repo tooling

Composer is used for builds, but no security-scanning tools are configured. This is a transparency and maintenance gap, though it is not by itself evidence that the release is unsafe.