fudge/dbal-repository

Release historydanger

The latest release was published in March 2016, with no releases in the last 12 months. This long release gap is strong evidence of abandonment risk.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with maintenance having stopped years ago.

Project backingcaution

The repository is owned by an individual rather than an organization. This is not inherently unhealthy, but it provides no organizational backing to offset the inactive history.

Repo issue activitycaution

There is no recent issue or pull request activity. With no recent commits or releases, this provides no evidence of active project support.

Repo toolingcaution

The repository uses Composer build tooling, but no security scanning tools are present. This is a modest transparency and maintenance gap, not a standalone severe risk.