naldz/dbpatcher-bundle

The package includes tests, a license file, and no install-time scripts, but it has no security scanning and only one open issue with no recent activity. Its small, user-owned project has little adoption evidence, so maintenance continuity is uncertain.

Latest v3.0.1

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was in August 2017, with zero releases in the last 12 months despite a long package history. This is strong evidence of abandonment risk.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with the long gap since the latest release and materially increasing abandonment risk.

Project backing

The repository is owned by an individual user rather than an organization. That is not inherently unhealthy, but it offers less visible backing for a project already showing no recent activity.

Repo issue activity

There was no new or closed issue or pull-request activity in the last month, and one issue remains open. This provides no evidence of current maintenance.

Repo package mention

The repository name does not match the package name and its README does not mention the package, creating uncertainty that the linked repository is the intended source.