sapientpro/module-wp-migration

Release historydanger

Only three releases were published, all within about four days, followed by roughly 19 months with no release. That leaves little evidence of sustained maintenance for a package developers may depend on.

Repo commit activitydanger

There were no commits and no active maintainers in the three months measured, while the last repository push was about 18 months ago. This is strong evidence of stalled maintenance, though not proof of abandonment by itself.

Package scaffoldingcaution

A README and changelog are present, and repository changelog support is reported. However, the README is still a generic GitLab setup template, so consumer documentation is weak; the absent tests are normal packaging practice.

Repo popularitycaution

The repository has zero stars and one fork, so there is little external adoption evidence. Popularity is only supporting evidence, but this provides no additional maturity signal.

Repo toolingcaution

Composer is used for the build, which is appropriate for this package, but no security scanning tools are configured. That weakens repository hygiene for a dependency handling migration functionality.