zyan/think-migration

The package has a valid license, a changelog, and only two runtime dependencies. Its consumer documentation is very brief, while the absence of a security policy and scanning reduces transparency; pin this version only if its migration behavior is already verified in your project.

Latest v3.0.3

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was in April 2022, with no releases in the last 12 months despite 17 releases overall. That leaves this release roughly four years and five months old and is strong evidence of stagnation.

Repo commit activity

The repository recorded 0 commits and 0 active maintainers in the last three months, consistent with the long release gap and raising abandonment risk.

Maintainers

Only one account has registry publishing access. That is a thin publishing base, and the provided repository activity does not show recent contributor capacity to offset it.

Package scaffolding

The artifact includes a changelog and a README, and the missing tests are normal packaging practice rather than a required artifact gap. The README is only 77 characters, so consumer guidance is limited.

Repo tooling

Composer is used for builds, but no security-scanning tools are configured. The missing scanning is a transparency and maintenance weakness rather than a severe risk by itself.