wpdesk/wp-migrations

This is a generally healthy, usable dependency with clear licensing, a substantial README and changelog, stable releases, a matching organization-owned repository, repository tests and build tooling, and no deprecation or dangerous workflow findings. The main concerns are that the repository shows no commits or active maintainers in the last 3 months, has no security policy or security-scanning tools, and its GitHub Actions workflow does not declare top-level permissions; these reduce transparency and maintenance confidence but are not sufficient to make the package unfit, especially given the release published on the assessment date and the repository's complete source scaffolding.

Latest 1.2.1

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

The repository records 0 commits and 0 active maintainers in the last 3 months, which is a genuine maintenance concern, although the latest release and repository push occurred on the assessment date.

Repo issue activity

There are no open issues or pull requests and no recent issue or pull-request activity. This is neutral-to-ambiguous for a small package, but offers little evidence of an active user or maintainer community.

Repo popularity

The repository has zero stars, forks, and watchers, which provides no external adoption evidence; this is a supporting gap rather than a decisive health problem for a small specialized library.

Repo tooling

Composer build tooling is present, but no security-scanning tools are configured, leaving a modest security-process and transparency gap.

Security policy

The repository has no security policy, so vulnerability-reporting expectations and disclosure handling are not documented.