io4n/yii2-dump

The repository has had no commits for nearly seven years, with no recent issue or pull-request activity. A single publisher and no security policy add maintenance and transparency concerns, though licensing, documentation, and package identity are clear.

Latest 1.0.8

Packagist

43%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published nearly seven years ago, and there have been no releases in the last 12 months. This is strong evidence of a dormant package for a database migration utility.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and leaving little evidence of ongoing maintenance.

Maintainers

One registry publisher account is responsible for the package, giving it a thin visible publishing base. The linked repository is user-owned rather than organization-backed, so there is little evidence of broader continuity if that maintainer stops working on it.

Project backing

The registry namespace and repository owner are the same individual user account, and no organization backing is shown. This provides a direct ownership link but limited evidence of institutional maintenance capacity.

Repo issue activity

There were no new or closed issues or pull requests in the last month, and no pull requests were open. Combined with the stale release history, this provides no sign of active project upkeep.