mike-sorokin/migration

Risky to adopt: the last release and repository activity are from September 2016, and the README explicitly calls this a development preview that should not be used in production. It has a clear MIT license, tests, and a usable README, but those strengths do not offset the long abandonment risk.

Latest 0.2.0

Packagist

30%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no release in nearly 10 years: its latest release was September 2016, with zero releases in the last 12 months. That sharply raises abandonment and compatibility risk.

Repository archived

The repository is not formally archived, which avoids an explicit abandonment marker, but it was last pushed in September 2016. The stale activity remains a serious maintenance concern.

Project backing

The package and repository are backed by the same individual account, so there is no ownership mismatch. However, the individual project has no demonstrated recent activity to compensate for the maintenance gap.

Repo issue activity

There have been no new issues or pull requests and no merged pull requests in the measured month. With the repository already inactive for years, this provides no evidence of ongoing maintenance.

Repo popularity

The linked repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but the absence of any visible adoption reinforces the concern created by the long inactivity.